In DB2 development, we see many customers that are NOT following RUNSTATS collection "Best Practices". But what are those best practices? The largest contributor to poor query performance is insufficient or misleading RUNSTATS. Improving the availability of pertinent and accurate statistics is a huge opportunity for customers to improve DB2 performance and reduce instability of access paths.
-
What are the most common RUNSTATS collection mistakes and how to avoid them?
-
How do I identify the right default statistics?
-
How do I handle statistics on tables that fluctuate dramatically in data volume?
In this session, we'll answer these questions and more as we discuss various runstats challenges and misconceptions.