wolfkillj (8/9/2012)
One way to see how much this issue is affecting your database would be to rewrite queries that join views to return the same results by querying the underlying tables directly, then comparing the execution plans, I/O stats, etc.
And this is remarkably easy to do!
Simply extract the VIEW code and put it into a CTE. If more than one VIEW is involved, use more than one CTE. If a VIEW references a VIEW, take that VIEW's code into a CTE also.
That whole process should take about 1 minute per VIEW. Then time the results of this query against the original. Voila! instant knowledge of whether there's an issue there.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St