Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dev:sql:statements:update_indexes:home [2010/07/30 18:02]
tdo
dev:sql:statements:update_indexes:home [2012/10/26 15:00] (current)
Line 38: Line 38:
  
   update indexes for column trans_table.trans_date;​   update indexes for column trans_table.trans_date;​
 +==== WIth Options ====
  
 +=== MAX_THREADS - Setting the number of processors used for indexing ===
 +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 - Setting the log directory ===
 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.
  
-  ​update indexes with log=odxlogs;+  ​UPDATE INDEXES WITH LOG=odxlogs;
  
 +  UPDATE INDEXES WITH LOG=c:​\mydatabase\log
 +
 +=== BUF - Setting the amount of indexing memory ===
 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. ​
  
Line 56: Line 66:
 > update indexes with log=odxlogs;​ > update indexes with log=odxlogs;​
 > setenv oa_max_rows > setenv oa_max_rows
-> update indexes with log=odxlogs;​ 
 > exit > exit
 os> os>
 
Back to top
dev/sql/statements/update_indexes/home.1280512968.txt.gz ยท Last modified: 2012/10/26 14:59 (external edit)