Jeff Moden (11/15/2012)
dwain.c (11/15/2012)
Jeff - Working through it now but its pretty deep and I expect it will take me awhile.Great explanations though!
I'm going to try to see if I can adapt the approach to another problem I encountered recently that is "not quite" a hiearchy.
Let me know if you decide to change your name to John. I have several article attributions to you I'll need to change.:-D
Thanks, Dwain. I'd be interested in your "not quite a hierarchy" problem. Sounds interesting.
Heh... nah. Not going to change my name. Too much paper work for us all. 😀
Seems you're up might late (or real early) today...
Did I say "I'm going to?" I meant to say "I may." In any event, don't expect much from me this weekend as I'm going fishing. Need to update my avatar. 😀
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