Overview | Environments | Databases | Tables | Constraints | Datatypes | Queries | Updates | Example

Omnidex can be deployed directly against an ODBC database. Omnidex retrieves and indexes the ODBC data, and queries read directly from the ODBC database as needed. This approach allows Omnidex to work alongside ODBC, providing a high-performance query environment for applications.

An Omnidex Environment File controls how Omnidex connects to the ODBC database and identifies the tables and columns that Omnidex will have access to. Omnidex accesses the ODBC data directly using standard SQL statements issued through the ODBC ODBC Connector. During indexing and query processing, Omnidex maintains a connection to the ODBC database and accesses the data as needed. Typically, queries are first routed to the Omnidex indexes where specific rowids or primary keys are identified that meet the criteria. Omnidex then fetches the appropriate rows using these values with standard SQL statements.

Omnidex does not migrate the data out of ODBC, but instead directly references the data in the ODBC database. This is not a requirement, though. Migration of the data into raw data files is an option if that is preferable; in fact, many companies use Omnidex Snapshots for this very purpose. Omnidex Snapshots are high-performing, highly-portable, heavily-indexed copies of data that can be easily accessed using standard ODBC and JDBC interfaces.

Omnidex is usually deployed on read-only tables. Most applications require tens to hundreds of Omnidex indexes on a table, making real-time updates impractical. Applications usually set aside certain ODBC tables that are refreshed on a regular basis and Omnidex indexes are completely refreshed. Omnidex does support real-time updates for those situations where there are fewer indexes and lower volume.

Next

See also: