Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

| DDL time(___8): .........4 milliseconds
| sql:
| COMMIT WORK
| DDL time(___9): .........4 milliseconds
| sql:
| DELETE FROM DDSTORAGE
| WHERE DBSYSABBR = 'DB2'
| AND TABNAME = '/BIC/ADSOTEST00'
| AND INDEXNAME = ''
| DDL time(___10): .........3 milliseconds
| sql:
| COMMIT WORK
| DDL time(___11): .........2 milliseconds
| Request for /BIC/ADSOTEST00 executed successfully
----------------------------------------------------------------------
The CREATE INDEX statement has the VALUES clause to determine the
partitions. As a result of executing this DDL:
► Table /BIC/ADSOTEST00 is a partitioned table.
► Index /BIC/ADSOTEST00~01 is a partitioned index — and it is also a
partitioning index.
► Index /BIC/ADSOTEST00~0 is a non-partitioned primary index.
We do not recommend using index-controlled partitioning. Table-controlled
partitioning is the recommended method, because it provides more support and
flexibility for partitioning tables and indexes.
7.5 DB2 compression
Since DataStore objects tend to be large (especially the active DataStore object
data, the /BIC/A00 table), we recommend using DB2
compression for these objects. There are several benefits to using DB2
compression, especially in the area of data management.
However, DB2 compression can also improve query performance on queries that
retrieve a large number of rows, like typical queries on DataStore objects. When
the data is compressed, more rows fit on a page. Therefore, more rows can fit
into the bufferpools providing a better buffer hit ratio and more rows can be
retrieved with less I/O.
132 Best Practices for SAP BI using DB2 9 for z/OS