Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
How to delete SQL server replication
On SQL Server 2008 R2, I am trying to setup transactional replication with test data and I'm getting an error:
SQL Server could not create publication PubOne.
Database 'distribution' does not exist.
This probably occurs because I previously tried to setup replication,
dropped my test databases, dropped distribution, and started over.
How do I fix this mess and truly start over?
Here's what I tried to delete replication:
alter database ReplicationSource set offline
alter database ReplicationTarget set offline
alter database distribution set offline
go
drop database ReplicationSource -- and remove disk files
drop database ReplicationTarget -- and remove disk files
drop database distribution -- and remove disk files
go
exec sp_removeDbReplication 'ReplicationSource'
exec sp_removeDbReplication 'ReplicationTarget'
go
exec sp_dropdistributor -- fails with Could not drop the Distributor 'DAVIDZ-PC'. This Distributor has associated distribution databases.
go
SQL Server could not create publication PubOne.
Database 'distribution' does not exist.
This probably occurs because I previously tried to setup replication,
dropped my test databases, dropped distribution, and started over.
How do I fix this mess and truly start over?
Here's what I tried to delete replication:
alter database ReplicationSource set offline
alter database ReplicationTarget set offline
alter database distribution set offline
go
drop database ReplicationSource -- and remove disk files
drop database ReplicationTarget -- and remove disk files
drop database distribution -- and remove disk files
go
exec sp_removeDbReplication 'ReplicationSource'
exec sp_removeDbReplication 'ReplicationTarget'
go
exec sp_dropdistributor -- fails with Could not drop the Distributor 'DAVIDZ-PC'. This Distributor has associated distribution databases.
go
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
sp_removedbreplication
This procedure should be used only if other methods of removing replication objects have failed. For more information about these methods.
To know more click on this https://technet.microsoft.com/en-us/library/ms152757(v=sql.105).aspx
This procedure should be used only if other methods of removing replication objects have failed. For more information about these methods.
To know more click on this https://technet.microsoft.com/en-us/library/ms152757(v=sql.105).aspx
Gentlemen,
The procedures you cite would have been great if I started with them. Unfortunately, I didn't know what I was doing, so I just dropped all relevant databases (distribution, replication source, replication target). But now the database server thinks replication is still going. How do I finally kill replication and start over?
The procedures you cite would have been great if I started with them. Unfortunately, I didn't know what I was doing, so I just dropped all relevant databases (distribution, replication source, replication target). But now the database server thinks replication is still going. How do I finally kill replication and start over?
Check if the query returns any '1' for the columns. If it does you need to update it to zero (0):
SELECT name, is_distributor, is_publisher, is_subscriber
FROM master.sys.servers
Victor,
I found 3 commands which seemed to do the trick:
exec sp_dropDistPublisher @publisher='MyPublisherNam
exec sp_dropDistributionDb distribution
exec sp_dropDistributor @ignore_distributor=1
I also executed your query and all columns came back as zero. I think it might even be fixed!
I found 3 commands which seemed to do the trick:
exec sp_dropDistPublisher @publisher='MyPublisherNam
exec sp_dropDistributionDb distribution
exec sp_dropDistributor @ignore_distributor=1
I also executed your query and all columns came back as zero. I think it might even be fixed!
Premium Content
You need an Expert Office subscription to comment.Start Free Trial