This shows you the differences between two versions of the page.
|
admin:features:segments:home [2012/03/05 20:53] doc |
admin:features:segments:home [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~NOTOC~~ | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | |||
| - | ====== Administration: Omnidex Features ====== | ||
| - | |||
| - | ===== Omnidex Segments ===== | ||
| - | |||
| - | **[[admin:features:segments:home|Overview]]** | | ||
| - | [[admin:features:segments:creating|Creating Segments]] | | ||
| - | [[admin:features:segments:queries|Querying Segments]] | | ||
| - | [[admin:features:segments:attaching|Attaching Segments]] |[[admin:features:segments:dropping|Dropping Segments]] | | ||
| - | [[admin:features:segments:archiving|Archiving Segments]] | ||
| - | ---- | ||
| - | |||
| - | ==== Overview ==== | ||
| - | |||
| - | Some applications process their queries in multiple steps. The first step isolates some rows based on a first group of criteria. The second step either refines those rows, or isolates a new set of rows based on a second group of criteria. At the end of the query, all of the steps are combined to produce a final result set. | ||
| - | |||
| - | With relational databases, these multi-step queries are often done by managing a series of temporary tables, usually containing only one column such as a primary key. Each step of the query refines these temporary tables, ultimately producing a final table with the final result set. This approach is significantly slower due to the writing and rewriting of the temporary tables; however, the need for this approach can be a fundamental requirement of the application. | ||
| - | |||
| - | Omnidex Segments provide a higher-speed approach to multi-step queries. Instead of writing and rewriting temporary tables, Omnidex Segments will record the index pointers for each step into temporary objects and allow those segments to be reused in future queries. These index segments are much more efficient than temporary tables, and can be directly applied against Omnidex indexes in future queries. This greatly improves the performance of multi-step queries. | ||
| - | |||
| - | |||
| - | ==== ==== | ||
| - | **[[admin:features:segments:creating|Next]]** | ||
| - | |||
| - | |||
| - | ====== Additional Resources ====== | ||
| - | |||
| - | See also: | ||
| - | |||
| - | {{page>:admin:features:see_also&nofooter&noeditbtn}} | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||