Snippet Name: INDEXES: SORT and NOSORT
Description: When creating an index, the default method Oracle uses to sort the index is in ascending order (SORT). However, if the rows are already stored in the database in ascending order you can use the NOSORT clause to skip the sorting process. Oracle will check to make sure that this is in fact the case and will return an error if the rows aren't actually in ascending order already. Normally you should use this clause when you first create or load the table.
If neither SORT or NOSORT is provided, Oracle will use SORT as the clause.
Also see:
» INDEXES: View table indexes
» INDEXES: Analyze Index
» INDEXES: Block Dump
» INDEXES: Rebuild Reverse
» INDEXES:
» INDEXES: ENABLE (function-based index)
» INDEXES: DISABLE (function-based index)
» INDEXES: Alter Index Parallel
» INDEXES: Alter Index Deallocate Unused
» INDEXES: Alter Index Allocate Extent
» INDEXES: Virtual / NoSegment
» INDEXES: Reverse Key Indexes
» INDEXES: Bitmap Join Indexes
» INDEXES: Bitmap Indexes
» INDEXES: Unique indexes
» INDEXES: Parallel Index
» INDEXES: Compute Statistics
» INDEXES: Function-Based Index
» INDEXES: DROP index
» INDEXES: Alter index
» INDEXES: Single Column Non-unique
» INDEXES: Index Usage Notes
» Compressed Indexes
» Create INDEX
Comment: (none)
Language: PL/SQL
Highlight Mode: PLSQL
Last Modified: March 10th, 2009
|
CREATE INDEX <index_name>
ON <table_name> (<column_name>)
PCTFREE <integer>
TABLESPACE <tablespace_name>
[SORT | NOSORT];
-- for example:
CREATE UNIQUE INDEX IDX_WS_INVOICE ON WS_INVOICE
(cust_num,order_year,client_code,note_id,record_id)
tablespace sales_us
nologging
nosort ; |
