| title | Secondary database is not joined | 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 | 10817e5e-75fa-42dd-baa2-359bea3ad051 | |
| caps.latest.revision | 14 | |
| author | MikeRayMSFT | |
| ms.author | mikeray | |
| manager | jhubbard |
| Policy Name | Availability Database Join State |
| Issue | Secondary database is not joined. |
| Category | Warning |
| Facet | Availability database |
This policy checks the join state of the secondary database (also known as a "secondary database replica"). The policy is in an unhealthy state when the dataset replica is not joined. The policy is otherwise in a healthy state.
Note
For this release of [!INCLUDEssCurrent], information about possible causes and solutions is located at Secondary database is not joined on the TechNet Wiki.
This secondary database is not joined to the availability group. The configuration of this secondary database is incomplete.
Use Transact-SQL, PowerShell, or SQL Server Management Studio to join the secondary replica to the availability group. For more information about joining secondary replicas to availability groups, see Joining a Secondary Replica to an Availability Group (SQL Server).
Overview of Always On Availability Groups (SQL Server)
Use the Always On Dashboard (SQL Server Management Studio)