This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:indexing:home [2009/12/09 22:22] els |
admin:indexing:home [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ~~NOTOC~~ | ||
| + | |||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| - | ====== Omnidex Indexing ====== | + | ====== Administration ====== |
| - | **[[admin:indexing:home|Overview]]** -> [[admin:indexing:indexes|Indexes]] -> [[admin:indexing:basic|Strategies]] -> [[admin:indexing:advanced|Advanced]] -> [[admin:indexing:installation|Installation]] -> [[admin:indexing:maintenance|Maintenance]] | + | ===== Introduction to Omnidex Indexing ===== |
| - | ===== Overview ===== | + | **[[admin:indexing:home|Concepts]]** | |
| + | [[admin:indexing:overview:indexes|Options]] | | ||
| + | [[admin:indexing:overview:creation|Creation]] | | ||
| + | [[admin:indexing:overview:strategies|Strategies]] | | ||
| + | [[admin:indexing:overview:activecounts|ActiveCounts]] | | ||
| + | [[admin:indexing:overview:powersearch|PowerSearch]] | | ||
| + | [[admin:indexing:overview:autocomplete|AutoComplete]] | | ||
| + | [[admin:indexing:overview:text|Text]] | | ||
| + | [[admin:indexing:overview:advanced|Advanced Strategies]] | ||
| - | Omnidex adds performance and flexibility to database applications. These benefits are achieved by a combination of the indexes and the [[admin:sqlengine:home|Omnidex SQL Engine]]. The indexes provide the basic speed and flexibility, while the SQL Engine analyzes statements and determines the best way to use the indexes. Omnidex is different than most SQL engines in that many indexes are used to fulfill a query. It is common for all criteria, table joins, aggregations and ordering to be satisfied in a coordinated effort between many indexes. Complex queries may even be satisfied without ever accessing the underlying data. | + | ---- |
| - | Three basic types of indexes allow SQL statements to be optimized. They also provide features such as textual searches, fuzzy searches and geographical searches. Omnidex indexes provide the bulk of Omnidex functionality, optimizing criteria, table joins, aggregations and ordering. QuickText indexes provide basic textual searches on columns like name and address fields, product descriptions and general text. FullText indexes provide sophisticated text indexing designed for large blocks of textual data. | + | === Indexing Concepts === |
| - | Omnidex also has advanced options that optimize complex or unusual situations. One example is Index Groups, in which multiple columns are indexed as though they were one column. Another example is geographic indexes which index latitude and longitude coordinates in preparation for geographic radius searches. | + | 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. |
| - | Indexes are installed by simply designating indexes on the columns involved in a query. There are times when indexing options are valuable, and there are also times when multi-column indexes are created. Once the indexes are designated, all indexes can be built concurrently, greatly reducing the time required to build the indexes. | + | Omnidex takes a completely different approach to indexing that other databases. Instead of adding a single index here and there, administrators are encouraged to index all of the columns used in criteria, table joins, aggregations, ordering, and in certain circumstances, even retrievals. Using this approach, most queries will be fulfilled through the indexes without having to access the database at all. |
| - | To learn more about Omnidex indexing, read the following sections: | + | That being said, indexing is not the answer to every problem. There are times to use indexes and times to avoid them. |
| - | - [[admin:indexing:indexes|Understanding Indexes]] | + | |< 80% 50% 50% >| |
| - | - [[admin:indexing:basic|Basic indexing strategies]] | + | ^ Use Omnidex indexes for ... ^ Avoid Omnidex indexes for ... ^ |
| - | - [[admin:indexing:advanced|Advanced indexing strategies]] | + | | isolating a small number of rows | retrieving a large number of rows | |
| - | - [[admin:indexing:installation|Index installation]] | + | | processing complex searches | single-use databases | |
| - | - [[admin:indexing:maintenance|Index maintenance]] | + | | using more flexible search options | | |
| + | | obtaining counts and aggregations | | | ||
| + | | joining multiple tables | | | ||
| + | | ordering a query result | | | ||
| - | ====== ====== | + | \\ |
| - | \\ | + | |
| - | ---- | + | it is useful to understand how Omnidex uses indexes to optimize each of these situations. This knowledge will help in choosing the best selection of Omnidex indexes and options. |
| - | \\ | + | [[admin:indexing:concepts:home | More >]] |
| - | + | ||
| + | ===== ===== | ||
| + | ---- | ||
| + | \\ | ||
| + | **[[admin:indexing:overview:indexes|Next]]** | ||
| - | The next section on Omnidex Indexing is [[admin:indexing:indexes|Omnidex Indexes]]. | ||
| + | ====== Additional Resources ====== | ||
| + | See also: | ||
| + | {{page>:admin:indexing:see_also&nofooter&noeditbtn}} | ||
| {{page>:bottom_add&nofooter&noeditbtn}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||