Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
No (more?) bloat with REINDEX command
Message
From
26/06/2001 07:34:04
 
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00523073
Message ID:
00523469
Views:
16
David,

I surely agree that the factors you name cause bloat. I even saw this in the limited test I ran.

It's also true that I jumped the gun when I simply ASSuMEd that a "single pass" reindex would be much much quicker than a rebuild. I have no idea what REINDEX now does internally. But I have come to infer that VFPs natural buffering (cacheing) can often give the same benefit as the "single pass" method.

As regards when the bloating caused by REINDEX disappeared, I suppose that it really is immaterial. I do find it disturbing that we seem to have to "stumble upon" discovery of changes to long accepted 'axioms' for VFP coding/feature usage. But that is another issue.

Cheers,

JimN

>Jim,
>
>Most CDX bloat is caused by the nonrecovery of space used by index tags that have been deleted. A lesser bloat is caused by B+ tree fragmentation caused by the normal insertion of records. I don't recall when the REINDEX command started recovering deleted tag space. I don't think it did back in FP2.x. It does in VFP5 and VFP6 which are the only versions I have on this machine. It is also quite possible that REINDEX effectively is doing 1) read the indexes, 2) delete tag all, issuing the individual index commands
>
SNIP
Previous
Reply
Map
View

Click here to load this message in the networking platform