Database Cannot Be Upgraded Because Its Non-release Version (539)

Msg 1813, Level 16, State 2, Line 1 Could not open new database 'Database2019'. CREATE DATABASE is aborted. Msg 948, Level 20, State 1, Line 1 The database 'Database2019' cannot be opened because it is version 904. This server supports version 869 and earlier. A downgrade path is not supported. The internal database versions for SQL Server aren. Database 'Northwind' cannot be upgraded because its non-release version (539) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database. Could not open new database 'Northwind'. Just in the process of moving all the databases over now and attaching them to the already existing service applications (although i dont know why the Microsoft documentation says you have to create them when they already exist) although i see that the User Profile service application cannot be updated with the restored database names so I am going to delete the existing one.

The Siebel Upgrade Wizard takes a master configuration file as input. This file contains environment information and a driver file name. The Siebel Upgrade Wizard executes the steps in the driver file to perform the upgrade. Because the Siebel Upgrade Wizard performs the steps in the driver file, it lists the steps in a state log.
For full-upgrade, safe-upgrade forbid-version, hold, install, keep-all, markauto, unmarkauto, purge, reinstall, remove, unhold, and unmarkauto: remove the user tag from all packages that are installed, removed, or upgraded by this command as if with the add-user-tag command.

Database Cannot Be Upgraded Because Its Non Release Version 539

I was consulting a client for migration from SQL 2014 to SQL 2016. They were using methodology discussed in books online here. https://msdn.microsoft.com/en-us/library/dn178483.aspx (Upgrading AlwaysOn Availability Group Replica Instances). Let us learn about how to fix error 946.

Pes 2014 game download for mobile. While doing that, they noticed that once they added SQL Server 2016 as secondary replica everything was looking great, but availability database on SQL Server 2016 were stuck in Synchronized / In Recovery in SSMS.

I have asked them to check SQL Server ERRORLOG on the secondary replica (SQL Server 2016) and found below the message.

Error: 946, Severity: 14, State: 1.
Cannot open database ‘ProdDB’ version 782. Upgrade the database to the latest version.

I asked to check sys.sysdatabases using below

Since databases are part of availability group and have not been recoveredvered yet, it’s expected to see that version and state as “In recovery”. Once we have failed over the databases to secondary replica and made it as primary everything was looking good and database on SQL 2012 were shown as Not Synchronizing because SQL Server doesn’t allow database secondary replicaplica to be of lower version.

One thing which I noticed is that once I upgraded old primary to SQL 2016 then also databases were not getting synchronized. To fix that I must run below command on current secondary replica which is now upgraded to SQL 2016.

Have you ever done upgrade of SQL in AlwaysOn availability group? How was your experience?

Database Cannot Be Upgraded Because Its Non-release Version (539)

Reference: Pinal Dave (https://blog.sqlauthority.com)

Database Cannot Be Upgraded Because Its Non Release Version 539