Skip to content

Latest commit

 

History

History
54 lines (42 loc) · 2.48 KB

File metadata and controls

54 lines (42 loc) · 2.48 KB
title Manually Fail Over a Database Mirroring Session (Transact-SQL) | Microsoft Docs
ms.custom
ms.date 03/14/2017
ms.prod sql
ms.prod_service database-engine
ms.service
ms.component database-mirroring
ms.reviewer
ms.suite sql
ms.technology
dbe-high-availability
ms.tgt_pltfrm
ms.topic article
helpviewer_keywords
failover [SQL Server], database mirroring
manual failover [SQL Server]
database mirroring [SQL Server], failover
ms.assetid 36218d61-b5f5-4194-905a-608e0e903db4
caps.latest.revision 32
author MikeRayMSFT
ms.author mikeray
manager craigg
ms.workload On Demand

Manually Fail Over a Database Mirroring Session (Transact-SQL)

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] When the mirrored database is synchronized (that is, when the database is in the SYNCHRONIZED state), the database owner can initiate manual failover to the mirror server. Manual failover can be initiated only from the principal server.

To manually fail over a database mirroring session

  1. Connect to the principal server.

  2. Set the database context to the master database:

    USE master;

  3. Issue the following statement on the principal server:

    ALTER DATABASE database_name SET PARTNER FAILOVER, where database_name is the mirrored database.

    This initiates an immediate transition of the mirror server to the principal role.

On the former principal, clients are disconnected from the database and in-flight transactions are rolled back.

Note

Transactions that have been prepared by using the [!INCLUDEmsCoName] Distributed Transaction Coordinator but are still not committed when a failover occurs are considered aborted after the database has failed over.

See Also

ALTER DATABASE Database Mirroring (Transact-SQL)
Manually Fail Over a Database Mirroring Session (SQL Server Management Studio)
Role Switching During a Database Mirroring Session (SQL Server)