Home Forums SQLServerCentral.com Editorials Pride in Azure SQL Database RE: Pride in Azure SQL Database

  • May 9, 2018 at 2:33 pm

    #1989955

    Steve Jones - SSC Editor - Monday, May 7, 2018 9:02 AM

    Jeff Moden - Saturday, May 5, 2018 4:13 PM

    While I agree that this all sounds absolutely wonderful, I wonder how much pride there will be when they do an automatic upgrade that has the same effect as 2014 SP1 had on a lot of people or like the "new and improved" cardinality estimator had on our core code. 😉

    I think you're overestimating how many people had problems. Some did, and I know you did, but lots of people didn't notice it or have significant issues. They also provided trace flags to ensure backwards compatibility with the old flag.

    My point is, if they had not provided a backwards compatible trace flag, we'd have been in deep Kimchi.  And, if we had SSIS doing anything worthwhile, 2014 sp1 stood a pretty good chance of killing the instance, which is why they had to recall and reissue sp1.  Too late if your instance was murdered by the bad change.

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