• Brad Schulz (8/5/2013)


    Hi Jeff...

    I appreciate you doing the time tests. Obviously I have to eat my words talking about "half the CPU". When I did comparisons between what I posted and the original code, that is, in fact, what I saw (in Profiler)... but it was very informal and was not as scientific as what you posted.

    As I said, I hadn't read through the last 3 years of posts (I came into this because SQLServerCentral had your SQLSpackle post at the top of their email blast of Friday... it wasn't until I clicked on the link that I found the article was 3 years old). But it's interesting to see the myriad of alternate solutions that have come in. Now that you posted your recent time tests, I'm going to have a look at them all.

    Best...

    --Brad

    Very cool. Thanks for stopping by, Brad. Your post reminnded me that I was lonng overdue on doinng such a test (which MVJ suggested quite a while back). A lot of good folks, including yourself, stepped up to the plate on trying to make things faster on this one. Ya just gotta love this commmunity! 🙂

    Hopefully, I'll find some time to resubmit the article with a link to the test post.

    Thanks, again, Brad.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)