• WayneS (8/25/2011)


    Jeff Moden (8/25/2011)


    Great article, Wayne, although I'm a bit surprised you didn't publish the million row performance findings (like you did on your blog) which shows just how big a performance and "reads" problem you can run into with this new functionality.

    Still, the new functionality will beat a cursor.

    Thanks Jeff,

    The editor already had me remove some significant sections to keep it simple for the join-challenged amongst us... wanted to keep this article about just the enhancements to the over clause, and not really go beyond that.

    Plus, it gave me a way to promote the blog when the running totals came up in the discussion thread. 😀

    BWAA-HAAA!!! Editors... what do they know? 😛 (Hi Steve!)

    Understood on all fronts. Thanks for the feedback, Wayne. And, I'll say it again, well done on the article and the blog both! 🙂

    --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)