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 06:59] tdo |
dev:sql:statements:update_indexes:home [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| <html><div align="center"><span style="color:red">DRAFT</span></div></html> | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| - | |||
| ====== Omnidex SQL: UPDATE INDEXES ====== | ====== Omnidex SQL: UPDATE INDEXES ====== | ||
| + | {{page>:sql_bar&nofooter&noeditbtn}} | ||
| + | |||
| ===== Description ===== | ===== Description ===== | ||
| - | UPDATE INDEXES will synchronize and build the Omnidex indexes for a connect Omnidex Environment. | + | UPDATE INDEXES will synchronize and build the Omnidex indexes for a connected Omnidex Environment. |
| + | |||
| + | 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> | ||
| + | UPDATE INDEXES [ FOR environment_object ] | ||
| + | [ ON [INSTANCE] instance_no ] | ||
| + | [ WITH options ] | ||
| + | </code> | ||
| - | Update Omnidex indexes | + | |
| + | ===== Discussion ===== | ||
| + | ==== UPDATE INDEXES ==== | ||
| + | If no qualifier is specified, the UPDATE INDEXES statement will build all the Omnidex Indexes for the connected Omnidex Environment. | ||
| <code> | <code> | ||
| - | UPDATE INDEXES [ FOR < ENVIRONMENT [environment] | + | os> odxsql |
| - | | DATABASE database | + | > connect odx.xml; |
| - | | TABLE table_spec | + | > update indexes; |
| - | | COLUMN column_spec | + | > exit |
| - | | INDEX index_spec > ] | + | os> |
| - | + | ||
| - | [ON [INSTANCE] instance] | + | |
| - | [WITH options] | + | |
| </code> | </code> | ||
| + | ==== UPDATE INDEXES FOR environment_object ==== | ||
| + | A specific Database, Table, Column, or Index object can be specified to limit the area to build the indexes. | ||
| + | update indexes for database db1; | ||
| - | + | update indexes for table trans_table; | |
| - | ===== Discussion ===== | + | update indexes for column trans_table.trans_date; |
| + | ==== WIth Options ==== | ||
| - | == arg1 == | + | MAX_THREADS=thread_count allows the setting of the maximum number of processors to be used during the update index process. |
| - | == arg2 == | + | update indexes with max_threads=4; |
| - | ===== Examples ===== | + | 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. |
| - | ==== Simple ==== | + | update indexes with log=odxlogs; |
| - | ==== 2nd example ==== | + | BUF=mega_bytes is used to increase the internal size of indexing buffers used by the Omnidex indexing operation. |
| + | |||
| + | 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}} | ||