This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
admin:indexing:overview:creation [2012/01/20 17:40] doc created |
admin:indexing:overview:creation [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ====== Administration ====== | ====== Administration ====== | ||
| - | ===== Omnidex Indexing ===== | + | ===== Introduction to Omnidex Indexing ===== |
| - | + | ||
| - | Omnidex provides a wide variety of indexing capabilities. The simplest applications may simply require a few indexes to be added, but other applications may use many more indexing capabilities. It is useful to get a quick overview of the indexing capabilities of Omnidex. Customers commonly purchase Omnidex for its basic indexing capabilities, only to discover there is more more available. | + | |
| [[admin:indexing:home|Concepts]] | | [[admin:indexing:home|Concepts]] | | ||
| Line 18: | Line 15: | ||
| [[admin:indexing:overview:autocomplete|AutoComplete]] | | [[admin:indexing:overview:autocomplete|AutoComplete]] | | ||
| [[admin:indexing:overview:text|Text]] | | [[admin:indexing:overview:text|Text]] | | ||
| - | [[admin:indexing:overview:advanced|Advanced]] | | + | [[admin:indexing:overview:advanced|Advanced Strategies]] |
| - | [[admin:indexing:overview:applications|Applications]] | + | |
| ---- | ---- | ||
| - | \\ | ||
| === Index Creation === | === Index Creation === | ||
| + | Omnidex takes a different approach to index creation than most databases. Most relational databases use the CREATE INDEX command to declare and populate the index. This means that each time an index is created, the table is sequentially fully scanned. While this approach means that the index is available as soon as the CREATE INDEX command completes, it becomes expensive when many indexes are being created. | ||
| + | |||
| + | Omnidex applications often have hundreds of indexes, and so Omnidex provides a more optimized, two-step approach to creating indexes. First, Omnidex indexes are declared using the CREATE TABLE or CREATE INDEX SQL statements. These statements declare all of the properties and options for the indexes, but they do not immediately populate the indexes. After the indexes are declared, they can all be populated at the same time using the UPDATE INDEXES command. This allows one table scan to be shared between all of the indexes, greatly improving performance. | ||
| + | |||
| + | Omnidex generally indexes at a rate of around 1 billion keywords per hour. A keyword is a word or value to be indexed. For non-textual fields, like state codes or postal codes, a keyword is a single value. For textual fields, keywords are parsed based on spaces and punctuation. | ||
| [[admin:indexing:creation:home | More >]] | [[admin:indexing:creation:home | More >]] | ||
| Line 36: | Line 36: | ||
| ====== Additional Resources ====== | ====== Additional Resources ====== | ||
| See also: | See also: | ||
| - | {{page>:admin:basics:see_also&nofooter&noeditbtn}} | + | {{page>:admin:indexing:see_also&nofooter&noeditbtn}} |
| {{page>:bottom_add&nofooter&noeditbtn}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||