| title | Availability database is suspended | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 05/17/2016 | |
| ms.prod | sql-server-2016 | |
| ms.reviewer | ||
| ms.suite | ||
| ms.technology |
|
|
| ms.tgt_pltfrm | ||
| ms.topic | article | |
| f1_keywords |
|
|
| helpviewer_keywords |
|
|
| ms.assetid | 6baee70f-848c-4e86-b20d-78875c0f82cb | |
| caps.latest.revision | 15 | |
| author | MikeRayMSFT | |
| ms.author | mikeray | |
| manager | jhubbard | |
| ms.workload | Inactive |
| Policy Name | Availability Database Suspension State |
| Issue | Availability database is suspended. |
| Category | Warning |
| Facet | Availability database |
This policy checks the state of data movement of the secondary database (also known as a "secondary database replica"). The policy is in an unhealthy state when the data movement is suspended. The policy is otherwise in a healthy state.
Note
For this release of [!INCLUDEssCurrent], information about possible causes and solutions is located at Availability database is suspended on the TechNet Wiki.
Data synchronization on this availability database might have been suspended because of the following:
-
Due to an error, the system might have suspended data synchronization.
-
The database administrator might have suspended data synchronization for maintenance purposes.
Resume data synchronization. If the issue persists, check the availability group in the Event log, and then diagnose why the system suspended data movement.
Overview of Always On Availability Groups (SQL Server)
Use the Always On Dashboard (SQL Server Management Studio)