| title | Data synchronization state of availability database is not healthy | |
|---|---|---|
| description | Identify possible causes for why the data synchronization state of database in an Always On availability group is not healthy. | |
| ms.custom | seodec18 | |
| ms.date | 05/17/2016 | |
| ms.prod | sql | |
| ms.reviewer | ||
| ms.technology | high-availability | |
| ms.topic | conceptual | |
| f1_keywords |
|
|
| helpviewer_keywords |
|
|
| ms.assetid | 4fd003e7-808e-4b0e-b28a-47d9f2616f06 | |
| author | MashaMSFT | |
| ms.author | mathoma | |
| manager | erikre |
Data synchronization state of availability database is not healthy for an Always On availability group
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md]
| 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.
Note
For this release of [!INCLUDEssCurrent], 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)
Use the Always On Dashboard (SQL Server Management Studio)