|
|
|
To ensure efficient usage in CPU time and I/O resources, you should run the RUNSTATS utility regularly and often.
The DB2 optimizer estimates the number of rows that are returned by every query predicate and uses these estimates to determine the optimum query access path. Bad estimates lead to a sub-optimal access path requiring additional I/O resources.
Accurate catalog statistics can maximize the likelihood of efficient data access. You should do the following:
| Copyright © 2012 CA. All rights reserved. |
|