• Jeff Moden (9/2/2013)


    dwain.c (9/2/2013)


    Jeff Moden (9/2/2013)


    Same goes for another atypical method (the "Multi-Pass" update) that a chap by the name of "Hugo" wrote.

    My curiosity has been piqued. Would this be Hugo Kornelski and where would this atypical method be elaborated?

    No. Different Hugo... Hugo Kornelis.

    Here's his original post on the subject...

    http://www.sqlservercentral.com/Forums/FindPost816917.aspx

    Here's the post where I made a suggestion that cut about a 1/3rd out of the duration (same thread)...

    http://www.sqlservercentral.com/Forums/FindPost816964.aspx

    Hah! Same Hugo but I forgot how to spell his name! :w00t:

    Thanks Jeff!


    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