Cadavre (10/14/2013)
I'm sure you already did it
Hehe... Yes I did actually. I didn't post my results because I'd call all of the results overall too close to call so I only threw it out there because I think the choice here ends up being one you'd make on readability rather than raw performance.
Or maybe not... depends on what your biggest priority is.
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