Skip to content

Latest commit

 

History

History
38 lines (30 loc) · 1.88 KB

secondary-database-is-not-joined.md

File metadata and controls

38 lines (30 loc) · 1.88 KB
title description author ms.author ms.date ms.service ms.subservice ms.topic f1_keywords helpviewer_keywords
Secondary database is not joined
Availability Database Join State checks the join state of the secondary database as part of policy based management for Always On availability groups.
MashaMSFT
mathoma
05/17/2016
sql
availability-groups
reference
sql13.swb.agdashboard.drp2joined.issues.f1
Availability Groups [SQL Server], policies

Secondary database is not joined

[!INCLUDE SQL Server]

Introduction

  • Policy Name: Availability Database Join State
  • Issue: Secondary database is not joined.
  • Category: Warning
  • Facet: Availability database

Description

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.

Possible Causes

This secondary database is not joined to the availability group. The configuration of this secondary database is incomplete.

Possible Solution

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).

See Also

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