Kbase P26943: How to prevent database fragmentation in Progress 8.x
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/01/2011 |
|
Status: Unverified
GOAL:
How to prevent database fragmentation in Progress 8.x
GOAL:
Can fragmentation be prevented in Progress version 8
FACT(s) (Environment):
All Supported Operating Systems
Progress 8.x
OpenEdge Database Category: Configuration
FIX:
There is no way that database fragmentation can be avoided in version 8.
Records are allocated as they are created; if the database is full, the database will grow to host the new records, which will be stored in an order hardly predictable a priori; on the other hand, if records have previously been deleted from the database Progress will try and reuse the space left by deleted records, but the order is again basically random.
A similar algorithm applies to indexes.
In addition to that, data blocks will contain records from any database table, and data blocks will be interleaved with index blocks.
There is nothing in version 8 that will prevent this from happening. In Progress 9 or later, Storage Areas type II can be employed to minimize database fragmentation.