Tuning SQL with Optim Query Tuner, Part 3, Workload capturing and tuning
Learn how to monitor and tune queries and workloads to improve application performance
From the developerWorks archives
Date archived: January 12, 2017 | First published: July 26, 2012
The previous articles in this series introduced the concept of access paths, showed you how to read an access path diagram in Optim Query Tuner and went through the methodology for tuning individual queries. Here in Part 3, a methodology for tuning SQL workloads is introduced. Learn how to use InfoSphere® Optim™ Query Workload Tuner to capture an SQL workload from different sources, gather statistics and index analyses, compare access plans, and perform plan lock-down and plan management. 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 advice to help the DB2 optimizer improve access, such as collecting necessary statistics and creating optimal indices.
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.