对象及访问方法相关的优化.pptVIP

* Key Compression Specify COMPRESS to enable key compression, which eliminates repeated occurrence of key column values and may substantially reduce storage. Use integer to specify the prefix length (number of prefix columns to compress). For unique indexes, the valid range of prefix length values is from 1 to the number of key columns minus 1 (the default value). For nonunique indexes, the valid range of prefix length values is from 1 to the number of key columns. The default prefix length is the number of key columns. Key compression is useful in many different scenarios, such as: In a nonunique regular index, Oracle stores duplicate keys with the row ID appended to the key to break the duplicate rows. If key compression is used, Oracle stores the duplicate key as a prefix entry on the index block without the row ID. The rest of the rows are suffix entries that consist of only the row ID. This same behavior can be seen in a unique index that has a key of the form (item, time stamp), for example, stock_ticker, or transaction_time. Thousands of rows can have the same stock_ticker value, with transaction_time preserving uniqueness. On a particular index block, a stock_ticker value is stored only once as a prefix entry. Other entries on the index block are transaction_time values stored as suffix entries that refer to the common stock_ticker prefix entry. In some cases, however, key compression cannot be used. For example, in a unique index with a single attribute key, key compression is not possible because there is a unique piece, but there are no grouping pieces to share. * Bitmap Indexes With bitmap indexes, you can store data that has few distinct values within the column, such as gender or job_title. The index consists of a range of rows stored in the index, and then a map of binary values for each key. The value is “on”, that is 1, if the key is true for that row. In the example on the slide, the value in the bitmap is on for only one color. The row item is