Difference between revisions of "DB INDEXSEQNO"
Yvonnemilne (Talk | contribs) |
Yvonnemilne (Talk | contribs) |
||
| (4 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | ''Deprecated in Recital 10'' | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| Line 11: | Line 7: | ||
==See Also== | ==See Also== | ||
| − | [[INDEX]], [[Upgrading]], [[USE]] | + | [[recitalconvert]], [[CONVERT]], [[INDEX]], [[Upgrading]], [[USE]] |
==Description== | ==Description== | ||
| − | The DB_INDEXSEQNO | + | The DB_INDEXSEQNO environment variable has been added to help with optimizing character and date indexes. The optimization is based on the use of the pseudo column SYNCNUM to ensure that all keys are unique. Every row/record in a table has a unique SYNCNUM value for that table. |
| − | When DB_INDEXSEQNO is set to true, any tables and indexes that have not previously been converted, will be converted to use the SYNCNUM optimization as they are opened. It is however recommended that you use " | + | When DB_INDEXSEQNO is set to true, any tables and indexes that have not previously been converted, will be converted to use the SYNCNUM optimization as they are opened. It is however recommended that you use "recitalconvert index" or "convert index" to manually convert your tables before setting DB_INDEXSEQNO to true. |
New rows added to tables will always have the SYNCNUM column updated with a new unique number regardless of the DB_INDEXSEQNO setting. Once .dbx files have been converted to use SYNCNUM optimization, the DB_INDEXSEQNO value has no effect. | New rows added to tables will always have the SYNCNUM column updated with a new unique number regardless of the DB_INDEXSEQNO setting. Once .dbx files have been converted to use SYNCNUM optimization, the DB_INDEXSEQNO value has no effect. | ||
| Line 25: | Line 21: | ||
==Products== | ==Products== | ||
| − | Recital | + | Recital, Recital Server |
[[Category:Documentation]] | [[Category:Documentation]] | ||
[[Category:Configuration]] | [[Category:Configuration]] | ||
[[Category:Environment Variables|INDEXSEQNO]] | [[Category:Environment Variables|INDEXSEQNO]] | ||
| + | [[Category:Deprecated]] | ||
Latest revision as of 11:09, 5 October 2010
Deprecated in Recital 10
Contents
Purpose
Used for data and character index optimization
See Also
recitalconvert, CONVERT, INDEX, Upgrading, USE
Description
The DB_INDEXSEQNO environment variable has been added to help with optimizing character and date indexes. The optimization is based on the use of the pseudo column SYNCNUM to ensure that all keys are unique. Every row/record in a table has a unique SYNCNUM value for that table.
When DB_INDEXSEQNO is set to true, any tables and indexes that have not previously been converted, will be converted to use the SYNCNUM optimization as they are opened. It is however recommended that you use "recitalconvert index" or "convert index" to manually convert your tables before setting DB_INDEXSEQNO to true.
New rows added to tables will always have the SYNCNUM column updated with a new unique number regardless of the DB_INDEXSEQNO setting. Once .dbx files have been converted to use SYNCNUM optimization, the DB_INDEXSEQNO value has no effect.
To disable SYNCNUM optimization after it has been enabled, you must set the value of DB_INDEXSQNO to false and then recreate all the index and tag files. Tag files will need to be recreated from scratch, so tables must be opened with USE