This statement is not correct, at least when Set Deleted is ON. In the classes I teach, I have a 1.5 million record table to illustrate the effects of having a tag and not having a tag on deleted records. The difference in performance is quite impressive.

Set Deleted On is an implicit filter on deleted records. As with any filter, for best performance, especially when dealing with a large data set, you should have an index on that filter expression.

In terms of being a burden, I don't quite understand that. Indexes always have to be maintained anyway. One additional index is really not that big of a deal.

My 2 cents...



>>By now it well known that the deleted() tag is almost always more of a burden than this does good.