>>Performance will also improve for SQL SELECT, if you provide an index for each table: Index on Deleted() tag ItsDeleted
>>This allows SQL to enforce the SET DELETED filter from the index file, without having to make reference to the table itself.
>
>A good point, Robin. And don't forget that you can speed up your SQLs by not having ANY order set in your base tables.

I've seen this before...but a question comes up: I have a lot of user selected orders. So does this mean it's worth storing the current tag to a variable, doing SET ORDER TO, and then restoring the order after the query?