Question

Should I keyword index when I run a data change job in Global Data Change (GDC)?

Answer

In deciding which option to choose, consider:

1. The size of the record set being changed.**
   1. For small sets of records, “Run records through keyword index” is more expedient.
   2. For large sets of records, dynamic.dc file growth may slow the process. Choose “Do not run records through keyword index” and run a keyword regen later (remember that Support recommends you keep the number of records changed to 10,000 or less per job).
2. Database size.
   1. Small databases may be able to choose “Run records through keyword index” every time.
   2. Large databases may need to skip keyword indexing and run keyword index regens later.
3. The current size of your dynamic keyword file.

** "Small" and "large" are relative terms - the impact of a record set of a certain size varies based on a number of factors (e.g., current condition of keyword files, available resources, other processes on server, etc.). A set of 10,000 records may be "small" in one context and "large" in another.

Additional Information

Related articles:
What are the symptoms of keyword index problems?
Who can run a keyword regen?
How many records can be imported at a time using bulk import?

Documentation:
Technical User’s Guide
Voyager UTIL Menu

• Article last edited: 24-Jan-2020