Post reply

Add SQL 2016 server to an existing SQL 2012 Availability Group?

  • December 6, 2016 at 11:17 am

    #323929

    Can a SQL 2016 server be added to an existing SQL 2012 Availability Group?

    Michael L John
    If you assassinate a DBA, would you pull a trigger?
    To properly post on a forum:
    http://www.sqlservercentral.com/articles/61537/

  • December 7, 2016 at 2:27 am

    #1916431

    I found this at below link, so no.

    An upgraded primary replica can no longer ship logs to any secondary replica whose SQL Server 2016 instance that has not yet been upgraded to the same version.

    https://msdn.microsoft.com/en-us/library/dn178483.aspx

    Catch-all queries done right [/url]
    Gail Shaw's Performance Blog[/url]

  • December 7, 2016 at 2:30 am

    #1916433

    You need same version

  • December 7, 2016 at 6:29 am

    #1916493

    If you have same Windows Server versions you can add SQL Server 2016 to the same AG, but when you change primary replica to SQL Server 2016 all synchronization will stop. If you have different Windows Server versions (like Win 2012 with SQL2012 and Win2016 with SQL2016)? you need to change cluster context to include SQL2016 node to the Win2012 cluster AG.

    Both options may be used only for migration from SQL2012 to SQL2016 because there is no way to switch cluster back after failover.

  • December 14, 2016 at 7:28 am

    #1917875

    tazzman (12/7/2016)

    If you have different Windows Server versions (like Win 2012 with SQL2012 and Win2016 with SQL2016)? you need to change cluster context to include SQL2016 node to the Win2012 cluster AG.

    Needs to be a Windows 2012 R2 cluster not 2012

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply