Remove Database Mirroring (SQL Server)
Published: May 17, 2016
Updated: May 17, 2016
Applies To: SQL Server 2016
This topic describes how to remove database mirroring from a database in SQL Server 2016 by using SQL Server Management Studio or Transact-SQL. At any time, the database owner can manually stop a database mirroring session by removing mirroring from the database.
In This Topic
Before you begin:
To remove database mirroring, using:
Follow Up: After Removing Database Mirroring
Requires ALTER permission on the database.
During a database mirroring session, connect to the principal server instance, in Object Explorer, click the server name to expand the server tree.
Expand Databases, and select the database.
Right-click the database, select Tasks, and then click Mirror. This opens the Mirroring page of the Database Properties dialog box.
In the Select a Page pane, click Mirroring.
To remove mirroring, click Remove Mirroring. A prompt asks for confirmation. If you click Yes, the session is stopped and mirroring is removed from the database.
To remove database mirroring, use the Database Properties. use the Mirroring page of the Database Properties dialog box.
Connect to the Database Engine of either mirroring partner.
From the Standard bar, click New Query.
Issue the following Transact-SQL statement:
ALTER DATABASE database_name SET PARTNER OFF
where database_name is the mirrored database whose session you want to remove.
The following example removes database mirroring from the AdventureWorks2012 sample database.
ALTER DATABASE AdventureWorks2012 SET PARTNER OFF;
If you intend to restart mirroring on the database
Any log backups taken on the principal database after mirroring was removed must all be applied to the mirror database before you can restart mirroring.
If you do not intent to restart mirroring
Optionally, you can recover the former mirror database. On the server instance that was the mirror server, you can use the following Transact-SQL statement:
RESTORE DATABASE database_name WITH RECOVERY;
If you recover this database, two divergent databases with the same name are online. Therefore, you need to ensure that clients can access only one of them—typically the most recent principal database.