sp_removedbreplication (Transact-SQL)

This stored procedure is executed at the Publisher on the publication database or at the Subscriber on the subscription database. The procedure removes all replication objects from the database in which it is executed, but it does not remove objects from other databases, such as the distribution database.


This procedure should be used only if other methods of removing replication objects have failed. For more information about these methods, see Removing Replication.

Topic link iconTransact-SQL Syntax Conventions


sp_removedbreplication [ [ @dbname = ] 'dbname' ]
    [ , [ @type = ] type ] 


  • [ @dbname=] 'dbname'
    Is the name of the database. dbname is sysname, with a default value of NULL. When NULL, the current database will be used.
  • [ @type = ] type
    Is the type of replication for which database objects are being removed. type is nvarchar(5) and can be one of the following values.


    Removes transactional replication publishing objects.


    Removes merge replication publishing objects.

    both (default)

    Removes all replication publishing objects.

Return Code Values

0 (success) or 1 (failure)


sp_removedbreplication is used in all types of replication.

sp_removedbreplication is useful when restoring a replicated database that has no replication objects needing to be restored.

sp_removedbreplication cannot be used against a database that is marked as read-only.


Only members of the sysadmin fixed server role can execute sp_removedbreplication.


-- Remove replication objects from the subscription database on MYSUB.
DECLARE @subscriptionDB AS sysname
SET @subscriptionDB = N'AdventureWorksReplica'

-- Remove replication objects from a subscription database (if necessary).
USE master
EXEC sp_removedbreplication @subscriptionDB

See Also


System Stored Procedures (Transact-SQL)

Other Resources

How to: Disable Publishing and Distribution (Replication Transact-SQL Programming)
Removing Replication

Help and Information

Getting SQL Server 2005 Assistance

Change History

Release History

14 April 2006

Changed content:
  • Updated the introduction to reflect that this procedure does not connect to other databases to remove objects, and that this procedure should be used only if other methods of removing replication objects have failed.