3-2模式对象管理(索引).docVIP

SRC: Oracle8i Administrator’s Guide(14) Managing Indexes Guidelines for Managing Indexes Creating Indexes Altering Indexes Monitoring Space Use of Indexes Dropping Indexes Guidelines for Managing Indexes Oracle provides several indexing schemes: B*-tree indexes (currently the most common) B*-tree cluster indexes hash cluster indexes reverse key indexes bitmap indexes function-based indexes domain indexes Indexes are logically and physically independent of the data in the associated table. Oracle automatically reflects changes to data, such as adding new rows, updating rows, or deleting rows, in all relevant indexes with no additional action by users. Create Indexes After Inserting Table Data You should create an index for a table after inserting or loading data (via SQL*Loader or Import) into the table. It is more efficient to insert rows of data into a table that has no indexes and then create the indexes for subsequent access. You must also create the index for a cluster before inserting any data into the cluster. If the index is extremely large, you may want to perform the following tasks. To Manage a Large Index: Create a new temporary segment tablespace. Alter the index creator’s temporary segment tablespace. Create the index. Remove the temporary segment tablespace and re-specify the creator’s temporary segment tablespace, if desired. Limit the Number of Indexes per Table There is a trade-off between the speed of retrieving data from a table and the speed of updating the table. Specify Transaction Entry Parameters By specifying the INITRANS and MAXTRANS parameters during the creation of each index, you can affect how much space is initially and can ever be allocated for transaction entries in the data blocks of an index’s segment. Specify Index Block Space Use When an index is created for a table, data blocks of the index are filled with the existing values in the table up to PCTFREE. Estimate Index Size and Set Storage Parameters The maximum size of a s