Tuning SQL with Optim Query Tuner, Part 2, Tuning individual queries
Learn how to monitor and tune queries and workloads to improve application performance
From the developerWorks archives
Date archived: January 12, 2017 | First published: May 19, 2011
The first article in this series introduced the concept of access paths and showed you how to read an access path diagram in Optim Query Tuner. In this article, a methodology for tuning individual queries is introduced. Using a sample query, you are shown how you can use Optim™ Query Tuner to go through the process. The process includes using query formatting and annotation, and analysis of the access plan, statistics, predicates, and indexes. The goal is to ensure that the IBM® DB2® optimizer is provided with the information it needs to make the best performance-based decisions for your DB2 queries, and to provide you with advice on things you can do to help the DB2 optimizer have more options for improving access, such as creating the necessary indexes.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.