• Thanks for the feedback, Andy.

    Ironically, I love revisions of SQL Server that are out of date, like 2005 and 2008. Think about it. They're as stable as they going to get and you don't have to worry about an SP or CU that's going to be a real killer such as what recently happened with 2014 or like the online rebuild of databases in 2012 causing corruption. Yeah, I might miss out on the newest bright shiny object until sometime well into the future but I don't have to worry about that new object being slower or causing problems. I also hate it when something that's incredibly useful or something that has been a part of the system nearly forever is suddenly deprecated for one reason or another.

    Since it would appear that they've fixed all the new and regression problems in 2012, we're finally upgrading from 2005 to 2012. We'll upgrade to 2016 sometime in 2018 or 2020 because I hate "death by early adoption". 🙂

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