Data synchronization state of availability database is not healthy


Published: May 17, 2016

Updated: May 17, 2016

Applies To: SQL Server 2016

Policy NameAvailability Database Data Synchronization State
IssueData synchronization state of availability database is not healthy.
FacetAvailability database

This policy rolls up the data synchronization state of all availability databases (also known as "database replicas") in the availability replica. The policy is in an unhealthy sate when any database replica is not in the expected data synchronization state. The policy is otherwise in a healthy state.

System_CAPS_ICON_note.jpg Note

For this release of SQL Server 2016, information about possible causes and solutions is located at Data synchronization state of some availability database is not healthy on the TechNet Wiki.

The data synchronization state of this availability database is unhealthy. On an asynchronous-commit availability replica, every availability database should be in the SYNCHRONIZING state. On a synchronous-commit replica, every availability database must be in the SYNCHRONIZED state.

Use the database replica policy to find the database replica with an unhealthy data synchronization state, and then resolve the issue at the database replica.

[Overview of Always On Availability Groups (SQL Server)](../Topic/Overview%20of%20Always On%20Availability%20Groups%20(SQL%20Server).md)
[Use the Always On Dashboard (SQL Server Management Studio)](../Topic/Use%20the%20Always On%20Dashboard%20(SQL%20Server%20Management%20Studio).md)

Community Additions