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 23:05] els |
admin:indexing:home [2012/10/26 14:51] (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 ====== | ====== Omnidex Indexing ====== | ||
| - | **[[admin:indexing:home|Overview]]** -> [[admin:indexing:indexes|Indexes]] -> [[admin:indexing:basic|Strategies]] -> [[admin:indexing:advanced|Advanced]] -> [[admin:indexing:installation|Installation]] -> [[admin:indexing:maintenance|Maintenance]] | + | **[[admin:indexing:home|Overview]]** | [[admin:indexing:indexes:home|Indexes]] | [[admin:indexing:strategies:home|Strategies]] | [[admin:indexing:activecounts:home|ActiveCounts]] | [[admin:indexing:powersearch:home|PowerSearch]] | [[admin:indexing:advanced:home|Advanced]] | [[admin:indexing:installation:home|Installation]] |
| ===== Overview ===== | ===== Overview ===== | ||
| - | 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. | + | Omnidex adds performance and flexibility to database applications. These benefits are achieved by a combination of the indexes and the [[admin:basics: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: Omnidex indexes, QuickText indexes and FullText indexes. 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. | Three basic types of indexes allow SQL statements to be optimized: Omnidex indexes, QuickText indexes and FullText indexes. 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. | ||
| + | |||
| + | ActiveCounts is an Omnidex indexing approach that allows applications to show criteria values and their counts at each step of a search. Users can see their choices and know how the counts would change before making their selection. This feature is especially valuable for businesses that allow online searching of their database through web applications. | ||
| + | |||
| + | PowerSearch is an Omnidex indexing approach that allows applications to activate a fuzzy search. The user can enter their best guess at the criteria, and then PowerSearch will use misspellings, phonetic searches, synonym lists and word forms to locate the data. This feature is especially valuable for applications that search for specific data based on a user's search terms. | ||
| 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 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. | ||
| Line 20: | Line 24: | ||
| - [[admin:indexing:indexes|Understanding indexes]] | - [[admin:indexing:indexes|Understanding indexes]] | ||
| - | - [[admin:indexing:basic|Basic indexing strategies]] | + | - [[admin:indexing:strategies|Basic indexing strategies]] |
| + | - [[admin:indexing:activecounts|ActiveCounts]] | ||
| + | - [[admin:indexing:basic|PowerSearch]] | ||
| - [[admin:indexing:advanced|Advanced indexing strategies]] | - [[admin:indexing:advanced|Advanced indexing strategies]] | ||
| - [[admin:indexing:installation|Index installation]] | - [[admin:indexing:installation|Index installation]] | ||
| - | - [[admin:indexing:maintenance|Index maintenance]] | + | |
| ====== ====== | ====== ====== | ||
| Line 34: | Line 40: | ||
| The next section on Omnidex Indexing is [[admin:indexing:indexes|Omnidex Indexes]]. | The next section on Omnidex Indexing is [[admin:indexing:indexes|Omnidex Indexes]]. | ||
| + | |||
| + | **[[admin:indexing:indexes|Next]]** | ||
| {{page>:bottom_add&nofooter&noeditbtn}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||