>Filtered indexes will not be faster than views, because they are ignored by Rushmore. IMHO, filtered index should not be used other than on a primary or candidate key because of that.
I have to argue with you on this because we tried using views just to extract a few hundred records from over 1 million records and we compared it to filtered indexes. And the difference is significant. IMO, rushmore also applies to filtered indexes because the logic behind it is the same with FOR, SET FILTER etc. which are RUSHMORE enabled.
>Ok, your argument is highly regarded. How about using many filtered indexes in a single table? I have that concern in mind because we are about to develop a Hospital System that we think we have to use huge filtered indexes. We primarily choosing this approach because it's much faster than set filter, views etc.
JESS S. BANAGA
Project Leader - SDD division
...shifting from VFP to C#.Net
CHARISMA simply means: "Be more concerned about making others feel good about themselves than you are in making them feel good about you."
