Remove a Secondary Database from a Log Shipping Configuration (SQL Server)
Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).
This topic describes how to remove a log shipping secondary database in SQL Server 2016 by using SQL Server Management Studio or Transact-SQL.
In This Topic
The log-shipping stored procedures require membership in the sysadmin fixed server role.
To remove a log shipping secondary database
Connect to the instance of SQL Server that is currently the log shipping primary server and expand that instance.
Expand Databases, right-click the log shipping primary database, and then click Properties.
Under Select a page, click Transaction Log Shipping.
Under Secondary server instances and databases, click the database you want to remove.
Click OK to update the configuration.
To Remove a Secondary Database
On the primary server, execute sp_delete_log_shipping_primary_secondary to delete the information about the secondary database from the primary server.
On the secondary server, execute sp_delete_log_shipping_secondary_database to delete the secondary database.
If there are no other secondary databases with the same secondary ID, sp_delete_log_shipping_secondary_primary is invoked from sp_delete_log_shipping_secondary_database and deletes the entry for the secondary ID and the copy and restore jobs.
On the secondary server, disable the copy and restore jobs. For more information, see Disable or Enable a Job.