June 2018
Intermediate to advanced
478 pages
10h 52m
English
If the table is small, it should probably not be compressed. There are thresholds required for a dictionary to be built. If there are not enough rows, or if the compression value is low, a dictionary might not be created, and therefore, no rows can be compressed.
It is possible to estimate the potential impact of compression on a table. The old method was to run the INSPECT command, and then format the results using db2inspf. The INSPECT command produces a file stored in the same location as the current db2diag.log file for that Db2 instance (a DIAGPATH database manager configuration parameter).
A better way is to make sure that valid statistics have been collected on the table by running the RUNSTATS utility. ...
Read now
Unlock full access