Kbase 20317: Instances of an index rebuild requirement
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/20/2008 |
|
Status: Unverified
GOAL:
Instances of an index rebuild requirement
GOAL:
When should indexes be rebuild?
GOAL:
When to rebuild indexes?
FACT(s) (Environment):
Progress 9.x
OpenEdge 10
FIX:
An index rebuild must be performed after:
- A bulk load.
A bulk load automatically deactivates a data table's index. The rebuild is run to reactivate the indexes.
- Manual deactivation of all indexes before a Data Dictionary load with previously dumped activated index tables.
The deactivation increases loading performance and improves the index creation process but an index rebuild is then required.
- A binary dump and load
This also deactivates indexes and therefore also requires an index rebuild.
The exception is when you use Version 9.1B and Higher. The PROUTIL utility for this version can simultaneously load data and build indexes during a binary load.
Prior Progress versions required that, upon completion of a binary load, you use the PROUTIL utility with the IDXBUILD qualifier to rebuild the indexes in the database.
A Progress dictionary dump and load is the only way to completely avoid the need for an index rebuild.
- After changing the DataBase Collation Table
- After changind the Word-Break Table