Kbase P17258: Can I have less than 64 records per block when a storage area is defined with 256 records per block?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Verified
GOAL:
Can I have less than 64 records per block when a storage area is defined with 256 records per block?
FIX:
Short answer: YES
Long answer:
It recommended that an additional storage area be defined for any table(s) whose records are large than to reserve 256 "slots" in each data block header and to use only a quarter of them.
For a database which uses an 8K block size, the limit on a storage area which has been defined using 64 records per block is 256GB, the limit on a storage area which has been defined using 256 records per block is 64GB.
For an index storage area, it is recommended that you leave the default number of records per block, unless you have index keys of 90 bytes and/or a table with a billion records or more (as you would benefit by changing the records per block by setting it to a smaller value than the default value).