Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Is it reasonable to have index on DELETED()?
Message
From
16/03/1999 08:15:32
Walter Meester
HoogkarspelNetherlands
 
 
To
15/03/1999 22:52:52
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00196021
Message ID:
00198009
Views:
52
Chaim,

>Hello Andrus,
>If you have a large table and you SET DELETED ON, then you need the index on DELETED() regardless of how many records are deleted. If you do not have an index on DELETED(), VFP has to inspect each record to determine whether or not to present it. Thus, you lose all Rushmore optimization.

This is simply NOT True. If you don't have a deleted() tag, rushmore still optimizes when it can use other indexes to optimize.

If you've got an invoices table with 1 milion records in it with only a few thousands deleted, and you want to select all the records with a particular article (with an index on article) you don't need a tag on deleted() because it runs in aprox. the same time as with a tag on deleted().

I personally find indexes on deleted a waste of diskspace and performance (when it comes to appending records).

Though an index enables fox to use full optimization it is NO guarantee that it will be faster than only a partial optimization.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform