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/08/04 14:49] tdo |
dev:sql:statements:update_indexes:home [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 39: | Line 39: | ||
| 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. | ||
| + | |||
| + | 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. | ||