Kbase P113930: When using Type II Storage Areas, what might cause higher fragmentation of records?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/01/2011 |
|
Status: Unverified
GOAL:
When using Type II Storage Areas, what might cause higher fragmentation of records?
GOAL:
What causes record fragmentation?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
OpenEdge Category: Database
FIX:
If records are created in a block and later the records are updated causing the size of the records to grow then the possibility exists that the new data being added to the record will not fit into the existing block the record was started in.
Updating records with information larger than the current block can hold may cause fragmentation regardless if the area is defined as Type I or Type II.
Based on changes beginning in OpenEdge 10.1A, record fragmentation has been dramatically reduced.
A record will have no more than 9 fragments total.
If a record is updated, the original recid that the record holds will be maintained.
The additional fragments may be repositioned as needed to keep the total number of fragments to 9 or less.
In some cases data fragments will be concatenated together within a new block to maintain this limit.