I have set up replication at many different organization. One error I quite commonly face is after I have removed replication I can not remove database. When I try to remove the database it gives me following error.
Cannot drop the database because it is being used for replication. (Microsoft SQL Server, Error: 3724)
Fix/Workaround/Solution:
The solution is very simple. Create the empty database with the same name on another server/instance first. Take full back of the same and forced restore over this database.
Do let me know if you have any better idea or suggestion.
Reference : Pinal Dave (https://blog.sqlauthority.com)
41 Comments. Leave new
EXEC sp_replicationdboption’AdventureWorks2014′,’publish’,false
Then we can go ahead and drop the database
I did this: right click on Replication -> Publisher Properties -> Publication Databases -> Un Select the Databases that were throwing error, click Ok. Again try the Delete Database operation, now it’s deleted successfully.
Yes. It worked for me. That’s a simple solution indeed!
Set it offline, then you should be able to drop it.
sp_removedbreplication ‘YourDB’
Go
drop database YourDB
Simply use this system procedure “sp_removedbreplication”
then drop your database normally.
This has worked for me, thanks
sp_removedbreplication databasename
Found a Neat way to do that. its just a single query : exec sp_removedbreplication ‘DB_NAME’
is there a way to script the process using powershell?
works cool