Difference between revisions of "SET FASTINDEX"
Yvonnemilne (Talk | contribs) |
Helengeorge (Talk | contribs) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
==Purpose== | ==Purpose== | ||
Quickly build temporary indexes | Quickly build temporary indexes | ||
| Line 27: | Line 23: | ||
==Products== | ==Products== | ||
| − | Recital | + | Recital Server, Recital |
[[Category:Documentation]] | [[Category:Documentation]] | ||
[[Category:Commands]] | [[Category:Commands]] | ||
[[Category:Set_Commands|FASTINDEX]] | [[Category:Set_Commands|FASTINDEX]] | ||
| + | [[Category:Indexing]] | ||
| + | [[Category:Indexing Set Commands]] | ||
Latest revision as of 15:44, 23 November 2009
Purpose
Quickly build temporary indexes
Syntax
SET FASTINDEX <ON | OFF>
See Also
Description
The Recital DBMS supports two types of index creation: normal and fast indexing. When SET FASTINDEX is set ON, index files will be built faster at the expense of a well balanced b-tree, this means updates will take longer because the tree is re-balanced as it is being used. When SET FASTINDEX is OFF, indexes may take longer to build, but will be completely balanced when the INDEX command has finished. This is the preferred method for creating indexes. Regardless of the method used to create the index, as keys are added, modified and removed from the index, balancing of the b-tree will continue. The SET FASTINDEX command has no effect when using the REINDEX command.
CAUTION: The intended proper use of SET FASTINDEX is for the rapid creation of temporary indexes that are only meant to be used once and then discarded. It is not recommended for building a permanent index of any kind.
Example
set fastindex off
Products
Recital Server, Recital
