This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 14.000000000000002%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
I have configured Distributed Availability Group (DAG) between two WSFC with the same SQL version (sql server 2016),
but now I want to configure the DAG with a different version of SQL Server (SQL Server 2016 and SQL server 2019), but arises error while configuration like 'Cannot open database 'test2' version 852. Upgrade the database to the latest version' and database status is Synchronized/In Recovery and it is mentioned that 'The database 'TEST' is marked RESTORING and is in a state that does not allow recovery to be run.' in SQL logs.
Two different things are mentioned in Microsoft documentation. I mark them in the following picture.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 66%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEM%3C/text%3E%3C/svg%3E)
Have you arrived at a solution for your issue? We are also experiencing this.
Thanks!
Eric
The only time you would have different versions of SQL Server in the same AG is when you are doing a rolling upgrade, and you are upgrading the nodes one at a time.
My question is about Distributed Availability Group which I mean different SQL Server version usage between two AG
But that does not change things. It also says in the document that you quote that the reason you would have different versions in a distributed AG is for migration. And, as I understand the text, in AG1 both nodes must be the same version, and the same is true for AG2. Did you do it that way.
Note also, that the second part you highlighted is about Windows Server, which has no relation to the error message you are getting.
Yes, in my configuration AG1 is SQL Server 2016 and AG2 is SQL Server 2019. First time I configured each AG with the same Sql version and different WIndows OS for migrating database servers from WIndows 2012 to Windows 2019, it was successfully.
But now I want to upgrade Sql Version at the same time migration from Sql Server 2016 to Sql Server 2019, but secondary AG(forwarder) is not healthy in DAG , database status is SYNCHRONIZED\IN RECOVERY
OK, if the purpose is migration, you are on the right track. I just wanted to point out that this was the only valid situations when you want to mix SQL Server versions in an (D)AG.
I don't have a lab environment to try this in. Hopefully someone can jump in ask the right questions about what you did.
According to MS document, the mix major versions of SQL Server in the same distributed availability group is only supported in upgrading and migrating scenarios.
Upgrade distributed Availability Group is different from traditional AG. To perform a rolling upgrade of a distributed availability group, first upgrade all of the secondary replicas. Next, failover the forwarder, and upgrade the last remaining instance of the second availability group. Once all other replicas have been upgraded, failover the global primary, and upgrade the last remaining instance of the first availability group. Please refer to General steps to upgrade a distributed availability group to get more information.
Best regards,
Cathy
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.