Jeff Moden (12/11/2013)
ChrisM@Work (12/11/2013)
Gosh, I'm surprised that with a title like this, there have been so few takers - and so little feedback from the OP. Maybe those sleepless nights have caught up. Here's a simple solution for starters.I don't know what's going on with the OP but when I see that ChrisM has worked a problem, I figure there's little left for me to do and move on. 😉
I feel the same way! 😀
I did look at this thread yesterday and saw that Chris suggested there was something wrong with the sample data/results so I passed on it at the time.
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