• PiMané (9/23/2013)


    dwain.c (9/23/2013)


    As Jeff said, NM=Nice Method (?).

    Except I think that P.[Path] should be p.Order_val in the recursive leg of your CTE.

    Yes, had to change it to work but it's just fine... 🙂

    Pedro

    Figured you must've.

    I looked at this in the morning but didn't have time, so I came back to study it. Any time Jeff approves of something it makes me want to understand.

    Now I think I do so I'm probably the better for it.


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    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