• Creating an index to tune a specific statement could affect other statements. • It is best to drop unused indexes. • EXPLAIN PLAN can be used to determine if an index is being used by the optimizer.
Keys frequently used in Keys and expressions with few search or query distinct values except bitmap expressions indexes in data warehousing Keys used to join tables Frequently updated columns High-selectivity keys Columns used only with functions or expressions unless creating function-based indexes Foreign keys Columns based only on query performance
• Inserts result in the insertion of an index entry in
the appropriate block. (Block splits might occur.) • Delete rows result in a deletion of the index entry. (Empty blocks become available.) • Updates to the key columns result in a logical delete and an insert to the index.
– Can use multiblock I/O – Can be parallelized • Index scans: – Allow index access only – Are followed by access by ROWID • Fast-full index scans: – Can use multiblock I/O – Can be parallelized
gather statistics about the usage of an index. • Benefits include: – Space conservation – Improved performance by eliminating unnecessary overhead during DML operations