At 21:10 15/10/2008, Anderson wrote:

>Hi,
>
>
>> I give in,... what's 'no reserve'
>
>It means the engine will not reserve space for record versions on the same
>page of the original record. This should not be used unless you have a
>READ-ONLY database since it will degrate performance.

More specifically, it will make the engine more likely to request more page blocks when it has to write a new record version.

I think the OP will improve things *generally* by backing up this database and restoring it and then setting this attribute off (gfix -use reserve) before putting the restored DB on line. This will also fix the chaotic state of the index pages that showed in the stats - which is pretty much what you'd expect where large chunks of deletes are being run regularly. They should plan to do some periodic index housekeeping, too.

But - an explanation for the apparent data loss? - don't know. Some quirk of OS caching on Vista during shutdown? Never heard of it before, except on systems where the software doesn't do the right thing in its destructors. In any case, it's a basic that the users should be trained to shut down *any* running application elegantly before heading for the Shutdown button....

./heLen