Hi Christof -

>I don't know about your applications, but in my application I use many selects that involve several tables. Also, I use a lot of Selects that return filtered sets, because I have to process a number of records. Here I don't want to create a physical table. In most of these Selects, an index on DELETED() improves performance in my applications.

I don't think we're arguing for no Deleted() index in all scenarios. I too have some situations (multi-table, filtered, and tables that potentially may have a lot of deleted records).

But my point, at least, is that the wisdom that it's a gospel rule (at least I had been led to believe this) to have a deleted index on any large table is not true. My largest tables (500 MB or so) have mostly single table, NOFILTER queries on them, and contain no deleted records. This is the situation where a deleted index makes no sense, so far as I can see...