  Step
6 - Populate and Maintain the Indexes
This section describes populating the Omnidex indexes using the DBINSTAL
utility, as well as various methods for maintaining them.
- New installations must first populate the index files. This is done
by with DBINSTAL using the B (build) command. This causes Omnidex to
read the database, filling the index files according to the index installation.
This must be done in all new installations but can also be done periodically
in existing installations.
- Existing installations have several options for keeping the indexes
up-to-date with the data. The Omnidex default is to automatically update
the indexes as the data is updated. However, in extremely high-volume
update applications, this might impede performance. Omnidex offers a
couple of options for updating the indexes separately from the data.
The application and user needs will govern which method is used to maintain
the indexes.
See Index
Maintenance for more information.
Batch Indexing
Batch
indexing is ideal for high-volume update applications that do not
require the indexes to be in synch with the data at all times. For example,
a sales application where sales transactions are uploaded to the server
nightly or weekly in a dat file, can be indexed nightly, or on a weekend
during off-peak hours. The application performance is not affected at
all by the indexing.
ODXAIM
Omnidex Automatic Index Maintenance, updates the indexes in a separate
process from the update application, with only a slight delay in index
synchronization. ODXAIM uses native database triggers to activate the
index updates.
OmniAccess API
OmniAccess
API custom applications can be written to run in the background to
update the indexes manually.
Top
|
