This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
admin:indexing:overview:strategies [2012/01/20 17:45] doc |
admin:indexing:overview:strategies [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]] | + | |
---- | ---- | ||
- | \\ | ||
=== Indexing Strategies === | === Indexing Strategies === | ||
- | The simplest strategy used in Omnidex is to index everything, or at least everything that is involved in the queries. This strategy immediately services a wide variety of queries. Most applications then benefit from analyzing the queries and using specific strategies for optimizing table joins, aggregations, grouping and ordering. | + | The simplest strategy used in Omnidex is to index everything, or at least everything that is involved in the queries. This strategy immediately supports a wide variety of queries. Each Omnidex index can be used in combinations with others, with each supporting a different aspect of the query, including criteria, table joins, aggregations and ordering. If all of the columns are indexed, most queries can be easily optimized. |
+ | |||
+ | Most applications then benefit from analyzing the queries and deciding on specific strategies for the most common queries. This is a good time to look at unusual search requirements, and take advantage of the indexing options and techniques that are available with Omnidex. | ||
- | Omnidex administrators will strive to have as much of the query processed within the index as possible. A query is consider fully optimized when all aspects are fulfilled by the indexes. In fact, queries that return counts, aggregations, or a few data columns can be fulfilled without ever accessing the data itself, even when the statements involve many table joins, complex criteria, group and ordering. | + | Omnidex administrators will strive to have as much of the query processed within the indexes as possible. A query is consider fully optimized when all aspects are fulfilled by the indexes. In fact, queries that return counts, aggregations, or a few data columns can be fulfilled without ever accessing the data itself, even when the statements involve many table joins, complex criteria, group and ordering. |
[[admin:indexing:strategies:home | More >]] | [[admin:indexing:strategies:home | More >]] |