sql 2016 upgrade from 2012 RRS feed

  • Question

  • good afternoon,

    I'm trying to find out if anyone has done an in-place upgrade form sql server 2012 enterprise with availability groups to sql 2016 enterprise.

    if so were their any issues that showed up?

    is this a typical upgrade path and do people do it?

    what type of down time is typically expected

    is the upgrade the same as you would for sql service packs? upgrade the secondary's then do the master? 

    Then would also like to know if you can join a sql standard 2016 to a sql enterprise 2012 server for a migration path? currently on enterprise and may be going to standard due to licensing costs. I believe the answer to this question is no but would some confirmation.

    Wednesday, October 19, 2016 7:02 PM

All replies

  • Hello,

    The following article may be useful:


    Availability Groups is an Enterprise Feature. SQL Standard is not viable. Meanwhile at the OS level, Windows Enterprise or Datacenter is required.

    Make sure failover is working fine before upgrading and the availability group is synchronized, Perform an integrity check on databases and perform database backups before upgrading.

    While upgrading, you can perform backups of the primary replica.

    Perform upgrade on the remote secondary replicas, after that upgrade the local secondary replicas, then failover the availability group, and upgrade the primary replica.

    Do not upgrade the primary first because transaction logs may not be sent to secondary replicas.

    Hope this helps.


    Alberto Morillo

    • Proposed as answer by Teige Gao Thursday, October 20, 2016 2:55 AM
    Wednesday, October 19, 2016 9:15 PM