November 13, 2014 at 8:29 pm
Hi all,
I am trying to add a 2014 replica to a 2012 primary availability group and am trying to understand if this is a supported setup.
When I set it up the 2014 replica is added but won't synchronize. The issue seems to be that when restoring the database it is left as NORECOVERY so it can be added to the AG. This means the database doesn't get upgraded from db level 706 and errors in synching or reading from. This tells me it can never work as it cannot be upgraded due to the way the database is added to the AG.
Msg 946, Level 14, State 1, Line 2
Cannot open database 'TestDB' version 706. Upgrade the database to the latest version.
Does anybody know a workaround for this?
Thanks in Advance!
November 14, 2014 at 1:47 am
I'm afraid it can't work.
Actually, it doesn't make sense, if you are using your AG replica for HA purposes.
If the AG failed over to the secondary (2014), it would never manage to fail back to the primary (2012) because the formats are different.
-- Gianluca Sartori
November 14, 2014 at 2:32 am
it's the same principal as mirroring from 2012 to 2014 or Log shipping from 2012 to 2014, it's a one time switch due to the version number increase and database internal upgrade
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 14, 2014 at 3:59 am
slim.richard (11/13/2014)
I am trying to add a 2014 replica to a 2012 primary availability group and am trying to understand if this is a supported setup.
Only supported as part of a rolling upgrade. In all other circumstances, the primary and secondary need to be the same version.
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
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply