>>> Attributes force write, no reserve
>
>> Having "no reserve" isn't a good option for a regular read/write production database, because this basically prevents having back record versions on the same page as the primary record version, thus additional page reads are necessary.
>
> Thanks Thomas!
>
> Is this by any chance related to the USE_ALL_SPACE option you have when restoring a database?

Correct.

> Or is GFIX the only way of updating it?

gfix also has an -use option, but this doesn't change the fill
distribution of existing pages.


--
With regards,
Thomas Steinmaurer
http://www.upscene.com/