This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:indexing:creation:updating [2012/01/26 16:20] doc |
admin:indexing:creation:updating [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ====== Administration: Omnidex Indexing ====== | ====== Administration: Omnidex Indexing ====== | ||
| - | ===== Indexing Creation ===== | + | ===== Index Creation ===== |
| [[admin:indexing:creation:home|Overview]] | | [[admin:indexing:creation:home|Overview]] | | ||
| [[admin:indexing:creation:declaring|Declaring Indexes]] | | [[admin:indexing:creation:declaring|Declaring Indexes]] | | ||
| **[[admin:indexing:creation:updating|Updating Indexes]]** | | **[[admin:indexing:creation:updating|Updating Indexes]]** | | ||
| - | [[admin:indexing:creation:standalone|Standalone Indexes]] | | ||
| [[admin:indexing:creation:files|Index Files]] | | [[admin:indexing:creation:files|Index Files]] | | ||
| - | [[admin:indexing:creation:updating|Maintenance]] | + | [[admin:indexing:creation:performance|Performance]] |
| + | ---- | ||
| ==== Updating Indexes ==== | ==== Updating Indexes ==== | ||
| - | When Omnidex indexing is added to an Omnidex Environment, only the metadata about each index is added to the environment. The indexes themselves are not built until an UPDATE INDEXES statement is issued. This is of great benefit since it allows multiple indexes to be built with one scan of the data. Omnidex applications frequently involve many Omnidex indexes, and building them individually would be prohibitively slow. The example below updates the indexes for a table. | + | When Omnidex indexing is added to an Omnidex Environment, only the metadata about each index is added to the environment. The indexes themselves are not populated until an UPDATE INDEXES statement is issued. This is of great benefit since it allows multiple indexes to be built with one scan of the table. Omnidex applications frequently use many Omnidex indexes, and building them individually would be prohibitively slow. The example below updates all of the indexes for a table. |
| <code> | <code> | ||
| Line 48: | Line 47: | ||
| </code> | </code> | ||
| + | If needed, an individual index can be populated without affecting the other indexes, so long as the index was created with the STANDALONE option. | ||
| + | <code> | ||
| + | > update indexes for index HOUSEHOLDS.STATE_CITY_ZIP; | ||
| + | Database | ||
| + | Table Rows CPU Elapsed | ||
| + | ---------------------------------------------------------------------------- | ||
| + | SIMPLE | ||
| + | HOUSEHOLDS 1,909 0:00 0:03 | ||
| + | ---------------------------------------------------------------------------- | ||
| + | Total 0:00 0:04 | ||
| + | |||
| + | Index (HOUSEHOLDS)HOUSEHOLDS.STATE_CITY_ZIP updated | ||
| + | > | ||
| + | </code> | ||
| ==== ==== | ==== ==== | ||
| - | **[[admin:indexing:creation:declaring|Prev]] | [[admin:indexing:creation:standalone|Next]]** | + | **[[admin:indexing:creation:declaring|Prev]] | [[admin:indexing:creation:files|Next]]** |