This is an old revision of the document!
Omnidex allows some relational database to use triggers to send INSERT, DELETE and UPDATE requests to Omnidex. For Oracle and Microsoft SQL Server, Omnidex allows triggers to be installed on a table that copy changes to a separate transaction table. The OdxAIM program can generate triggers for tables with Omnidex indexes. These triggers log the changes to the data in a separate, intermediate transaction table, and then OdxAIM processes this transaction table in the background to update the Omnidex indexes. This approach preserves transactional integrity, though there is a short delay between the updates of the database and the indexes.
This triggered approach is appropriate for a low volume of updates. Relational database triggers will require additional resources from the database, as will the logging and processing into the transaction table. This is in addition to the resources required to update the Omnidex indexes, as discussed in Online Updates. This approach is not recommended for large volumes of updates.
See also: