This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dev:sql:statements:update_indexes:home [2010/07/02 18:56] tdo |
dev:sql:statements:update_indexes:home [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| If only the Omnidex index specification needs to be synchronized, use the INSTALL INDEXES statement. This is typically used when converting between two releases. | If only the Omnidex index specification needs to be synchronized, use the INSTALL INDEXES statement. This is typically used when converting between two releases. | ||
| - | |||
| ===== Syntax ===== | ===== Syntax ===== | ||
| <code> | <code> | ||
| UPDATE INDEXES [ FOR environment_object ] | UPDATE INDEXES [ FOR environment_object ] | ||
| - | [ON [INSTANCE] instance] | + | [ ON [INSTANCE] instance_no ] |
| - | [WITH options] | + | [ WITH options ] |
| </code> | </code> | ||
| Line 31: | Line 30: | ||
| os> | os> | ||
| </code> | </code> | ||
| - | |||
| ==== UPDATE INDEXES FOR environment_object ==== | ==== UPDATE INDEXES FOR environment_object ==== | ||
| A specific Database, Table, Column, or Index object can be specified to limit the area to build the indexes. | A specific Database, Table, Column, or Index object can be specified to limit the area to build the indexes. | ||
| Line 39: | Line 37: | ||
| update indexes for table trans_table; | update indexes for table trans_table; | ||
| - | update indexes for column trans_table.trans_date;==== WITH Options ==== | + | update indexes for column trans_table.trans_date; |
| + | ==== WIth Options ==== | ||
| + | |||
| + | MAX_THREADS=thread_count allows the setting of the maximum number of processors to be used during the update index process. | ||
| + | |||
| + | update indexes with max_threads=4; | ||
| LOG=<directory> will cause Omnidex to write indexing logs to the specified directory. This is particularly useful for reviewing the status of large UPDATE INDEX operations. The directory has to be created before the UPDATE INDEXES statement is used. | LOG=<directory> will cause Omnidex to write indexing logs to the specified directory. This is particularly useful for reviewing the status of large UPDATE INDEX operations. The directory has to be created before the UPDATE INDEXES statement is used. | ||
| Line 47: | Line 51: | ||
| UPDATE INDEXES WITH BUF=1024 | UPDATE INDEXES WITH BUF=1024 | ||
| + | |||
| ===== Examples ===== | ===== Examples ===== | ||
| The following example will create a logging directory relative to the current directory that Omnidex will use to write indexing information during the index process. The example also uses the OdxSQL SETENV command to set the OA_MAX_ROWS environment variable to limit the maximum number of reads for each table to 100,000 rows to facilitate testing. | The following example will create a logging directory relative to the current directory that Omnidex will use to write indexing information during the index process. The example also uses the OdxSQL SETENV command to set the OA_MAX_ROWS environment variable to limit the maximum number of reads for each table to 100,000 rows to facilitate testing. | ||