2 Seat Sand Rail Plans Free

index compression in SAP environments

index compression is supported for SAP from Oracle 10g. Only B * Tree indexes are compressed, but no bitmap indexes (which are created by using bitmaps have to save space). Please also note 1109743

index compression is worthwhile especially if there are leading index columns that have a few forms and accounts for a relatively large proportion of the total index-column length. The optimal number of columns to be compressed by default, can be determined in accordance with Note 1109743rd This approach has the advantage that it is based on CBO statistics, and therefore quite fast and requires no locks.

Alternatively ANALYZE INDEX VALIDATE STRUCTURE also be used as described below in certain situations. Note, however, that leads to VALIDATE STRUCTURE locks and therefore should not be carried out in parallel with the production operation. Moreover, this operation can not be parallelized, so it may lead to longer run times:
ANALYZE INDEX "" VALIDATE STRUCTURE;

Then the table INDEX_STATS the Komprierungsinformation be taken, for example: SELECT
OPT_CMPR_COUNT, OPT_CMPR_PCTSAVE FROM INDEX_STATS;
OPT_CMPR_COUNT OPT_CMPR_PCTSAVE
-------------- ---------------- 2 22

beats Oracle in this case before a compression of the two leading index columns and anticipation of a reduction in net index data by 22 percent. With current

BRSPACE versions may also be performed with integrated INDEX REBUILD COMPRESS using the "CBB" option. Example of a compression index of the first two columns:
BRSPACE idrebuild-f-i-INDEX NAME CBB 2