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 07:21] 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 40: | Line 38: | ||
| update indexes for column trans_table.trans_date; | update indexes for column trans_table.trans_date; | ||
| + | ==== WIth Options ==== | ||
| - | ==== WITH Options ==== | + | MAX_THREADS=thread_count allows the setting of the maximum number of processors to be used during the update index process. |
| - | 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. | + | |
| - | update indexes with log="odxlogs"; | + | 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. | ||
| + | |||
| + | update indexes with log=odxlogs; | ||
| BUF=mega_bytes is used to increase the internal size of indexing buffers used by the Omnidex indexing operation. | BUF=mega_bytes is used to increase the internal size of indexing buffers used by the Omnidex indexing operation. | ||
| UPDATE INDEXES WITH BUF=1024 | UPDATE INDEXES WITH BUF=1024 | ||
| + | |||
| + | ===== 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. | ||
| + | <code> | ||
| + | os> odxsql | ||
| + | > connect myenv.xml; | ||
| + | > create directory odxlogs; | ||
| + | > setenv oa_max_rows=100000; | ||
| + | > update indexes with log=odxlogs; | ||
| + | > setenv oa_max_rows | ||
| + | > update indexes with log=odxlogs; | ||
| + | > exit | ||
| + | os> | ||
| + | </code> | ||
| {{page>:bottom_add&nofooter&noeditbtn}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||