The storage options specify the distribution scheme of an index. You can use the IN clause to specify a storage space for the entire index, or you can use the FRAGMENT BY clause to fragment the index across multiple storage spaces.
Storage Options: |--+-IN--+-dbspace---------------+-----------+------------------| | | (1) | | | +--------dbslice--------+ | | | (2) | | | '--------+-extspace-+---' | | '-TABLE----' (3) | '-| FRAGMENT BY Clause for Indexes |------'
Element | Description | Restrictions | Syntax |
---|---|---|---|
dbslice | The dbslice that contains all of the index fragments | Must exist | Identifier |
dbspace | The dbspace in which to store the index | Must exist | Identifier |
extspace | Name assigned by the onspaces command to a storage area outside the database server | Must exist | See the documentation for your access method. |
If you specify any storage option (except IN TABLE), you create a detached index. Detached indexes are indexes that are created with a specified distribution scheme. Even if the distribution scheme specified for the index is identical to that specified for the table, the index is still considered to be detached. If the distribution scheme of a table changes, all detached indexes continue to use the distribution scheme that the Storage Option clause specified.
For information on locally detached and globally detached indexes, see FRAGMENT BY Clause for Indexes. If you are using Extended Parallel Server, you cannot use the CLUSTER option and storage options in the same CREATE INDEX statement. See CLUSTER Option.
Enterprise Edition Home | Express Edition Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]