When you set up deferred indexing, you choose which indexes to process immediately and which to defer. Deferred indexing provides two main features that aid in the processing of your indexes:
Important: Although the system allows up to 255 queues, SirsiDynix strongly recommends you start with a single deferred queue. (For information about setting up multiple queues, see Setting Up Complex Deferred Indexing .)
QIndex works by reading a series of rows from the mq_index_queue table and then processing these entries on a record-by-record basis for a queue. The mq_index_queue table is a list of records that QIndex needs to index. After a record has been indexed, QIndex deletes the queue rows for that record (the deletion is part of the same database transaction as the indexing itself).
You defer processing of specific indexes by ranking indexes on level of necessity. In general, you can group your indexes into these two categories:
Here is an example of how deferred indexing works:
Workstation |
Indexes |
Time per Record |
Technical Workstation |
12 fundamental, non-deferred indexes |
2 seconds |
QIndex Workstation |
68 specialized and public indexes |
36 seconds |
In this example, Horizon indexes the 12 fundamental, non-deferred indexes on your technical workstation when a record is saved. At the same time, the 68 deferred indexes are indexed on the QIndex workstation. Although QIndex will fall behind because it has more work to do, it can catch up during times when large amounts of MARC data is not being saved. Because QIndex operates on its own workstation, your staff is not kept waiting while QIndex processes the indexes.
This section explains these topics:
• | Assigning Indexes for Deferred Indexing |
• | Starting QIndex |
© 1998-2017 Sirsi Corporation