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.

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for 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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!