AlwaysOn between SQL Server 2012 and 2014 possible?

  • Hi there,

    does anyone know if there is a way to create a Availability Group between SQL Server 2012 and 2014?

    If I am using the Wizard everything seems fine, but after finishing the secondary replica stays in the mode "Synchronized / In Recovery". (should be accessable)

    If I try to explizit join

    ALTER AVAILABILITY GROUP [test] JOIN;

    I get this error:

    Msg 41158, Level 16, State 3, Line 1

    Failed to join local availability replica to availability group 'test'. The operation encountered SQL Server error 41106 and has been rolled back. Check the SQL Server error log for more details. When the cause of the error has been resolved, retry the ALTER AVAILABILITY GROUP JOIN command.

    If Resume the HADR

    ALTER DATABASE [test] SET HADR RESUME

    It doesn't show any error.

    Am I waisting my time?

    The system have currently this software state.

    SQL Server 2014 CU7

    SQL Server 2012 SP2 CU5

    Cheers,

    Christian

  • christian_t (5/19/2015)


    Am I waisting my time?

    Yes.

    Cross-version is only for rolling upgrades, not as a permanent scenario.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Hi Gila,

    do you have any M$ documentation for that?

    I did not find anything in the description of the SQL Server 2014 descriptions and Upgrade Advisors.

    🙁

    Christian

  • https://msdn.microsoft.com/en-us/library/ff878487.aspx -- the 2014 BoL

    Each server instance must be running the Enterprise Edition of SQL Server 2014.

    https://msdn.microsoft.com/en-us/library/ff878487(v=sql.110).aspx -- the 2012 BoL

    Each server instance must be running the Enterprise Edition of SQL Server 2012.

    Not "Each server instance must be running the Enterprise Edition of SQL Server 2012 or 2014."

    Same as Database mirroring (probably with more restrictions on versions), since you cannot restore down-version (nor can log records be moved down-version), you can't have a 2014 primary replica with 2012 secondary replias. Similar to log shipping, if you have the secondary on a higher version (as part of a rolling upgrade), it won't be readable because of conversions going on.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • the devil is in the details...

    Thx for clarifying this

    Christian

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

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