Home Forums SQL Server 2016 SQL Server 2016 - Administration SQL 2012 to 2016 - Possible Application Issues RE: SQL 2012 to 2016 - Possible Application Issues

  • July 1, 2016 at 5:44 pm

    #1888179

    Br. Kenneth Igiri (6/27/2016)

    In upgrading from SQL Server 2012 to 2016, based on your experience, what are possible impacts the upgrade could have on an application that was built for SQL 2012? Please share any reference to documentation. Thanks so much.

    First, download and use the "Upgrade Advisor". It's not a panacea but it finds a bunch of things... even some that existed that should have been upgraded due to deprecation that may still be in effect.

    The second thing is that if you're doing an "in place" upgrade, I recommend you start with your staging box. You can't live without your development box and you can't live without your production box but you can live without your UAT box for a bit if something goes wrong.

    I recommend the same thing if you're doing a migration to new hardware but there's a fair bit more work in doing that especially if you have any of the SQL Server 4 letter words (SSIS, SSRS, SSAS, SSDT, etc) that must also be migrated. Full text migrations can be a bit testy, as well.

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