This shows you the differences between two versions of the page.
dev:sql:statements:update_indexes:home [2010/07/02 07:14] tdo |
dev:sql:statements:update_indexes:home [2016/06/28 22:38] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{page>:top_add&nofooter&noeditbtn}} | ||
- | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
- | ====== Omnidex SQL: UPDATE INDEXES ====== | ||
- | ===== Description ===== | ||
- | |||
- | UPDATE INDEXES will synchronize and build the Omnidex indexes for a connected Omnidex Environment. | ||
- | |||
- | ===== Syntax ===== | ||
- | <code> | ||
- | UPDATE INDEXES [ FOR < ENVIRONMENT [environment] | ||
- | | DATABASE database | ||
- | | TABLE table_spec | ||
- | | COLUMN column_spec | ||
- | | INDEX index_spec > ] | ||
- | [ON [INSTANCE] instance] | ||
- | [WITH options] | ||
- | </code> | ||
- | |||
- | |||
- | |||
- | ===== Discussion ===== | ||
- | |||
- | ==== UPDATE INDEXES ==== | ||
- | If no qualifier is specified, the UPDATE INDEXES statement will build all the Omnidex Indexes for the connected Omnidex Environment. | ||
- | ==== UPDATE INDEXES FOR 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; | ||
- | |||
- | update indexes for column trans_table.trans_date; | ||
- | ==== WITH Options ==== | ||
- | 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"; | ||
- | |||
- | BUF=mega_bytes is used to increase the internal size of indexing buffers used by the Omnidex indexing operation. | ||
- | |||
- | UPDATE INDEXES WITH BUF=1024 | ||
- | |||
- | {{page>:bottom_add&nofooter&noeditbtn}} |