Overview | Servers | Environments | Queries | Updates | Integration Guides
Omnidex is often used to increase performance and improve flexibility on relational databases. Most companies that have invested in a relational database solution will continue to use the relational database as their core data store, but they may want to improve query performance or enhance their searches with ActiveCounts, PowerSearch or AutoComplete. Omnidex can access the data in the relational database and provide a high-speed query environment.
One of the first decisions for the administrator is which tables Omnidex should access. Omnidex applications often have tens or hundreds of indexes per table, delivering extremely high performance. The overhead for real-time updates on hundreds of indexes can be substantial, and as such, Omnidex is not a good solution for indexing a high-OLTP system. If applications are going to heavily index the data, Omnidex should be pointed to separate tables that are periodically refreshed. If the data is not heavily updated or if the Omnidex indexing is minimal, then real-time updates remain an option.
Omnidex is most commonly installed on read-only tables that are periodically refreshed. Some companies discover that Omnidex can also provide a complete SQL engine against raw data files. This introduces the possibility of creating low-cost, high-performance, autonomous query environments using data extracted from the relational database. These can be placed on a separate server, alleviating the load on the relational database while improving performance and increasing scalability. This can also lower licensing costs for the overall application.
See also: