Mike,
>
>Well, considering the set filter so totally outperformed the dynamic index, it's not really an issue. I guess the point I'm coming to see is NOT everything should be part of an application. There have to be some worst practices if there are also best practices.

I would not call it worst practice, more in the line of "unfit for the present situation" - you have the code and can check on the different scenarios it will be used in, but there are use cases for filtered indices.

When I resort to a filtered index it is very often after a frustrating wait, which led to timing the situation "loosely" (measuring seconds() wrapped around a snipped piece of code) and comparing that to the perf of a filtered index. As long as there is no other index order needing to be followd, Rushmored Filter wins by a far margin.

But if you are looking for worst practices, search for antipatterns <bg>. As long as you only read about them, it is sorta gruesome humour. If you encounter them in the code you are asked to review, enhance or maintain, the fun is shrinking <g>.

regards

thomas