FIX: Secondary replica in "not healthy" state after you upgrade the primary database in SQL Server 2016

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Standard


After you upgrade an availability database on the primary replica that contains Memory-optimized tables from Microsoft SQL Server 2014 to Microsoft SQL Server 2016, if any secondary database replays the transaction log of the primary database, a dump file is created, and the secondary replica stops syncing with the primary replica. Additionally, the secondary replica is marked as "not healthy".

Note The secondary replica resumes normal operations after a restart.


Cumulative Update information

This issue was first fixed in the following cumulative update of SQL Server.


To work around this issue, restart the secondary replica.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.