Data synchronization state of availability database is not healthy

THIS TOPIC APPLIES TO: yesSQL ServernoAzure SQL DatabasenoAzure SQL Data Warehouse noParallel Data Warehouse


Policy Name Availability Database Data Synchronization State
Issue Data synchronization state of availability database is not healthy.
Category Warning
Facet Availability 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.


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

Possible Causes

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.

Possible Solution

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.

See Also

Overview of Always On Availability Groups (SQL Server)
Use the Always On Dashboard (SQL Server Management Studio)