Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Replication Issues

Status
Not open for further replies.

MattK

Technical User
Nov 11, 2002
15
AU
Hello all,

Our company has recently expanded into the USA (we were previously based in Australia), and before the 'USA team' left, I was playing around with replication between our local SQL server and the server they took with them.

Once I was done playing, I removed the publication on our local server, which seemed to work ok (it was removed from the list of publications), and it brought up a message saying I would have to manually remove the subscription on the subscriber.

So far so good, but now I have two problems - the subscribing server still lists it's subscription to the (now gone) publication under Replication -> Subscriptions, and I can't for the life of me get rid of it (which is a problem as it means I can't edit/delete from the target database). Also, on the publisher, even though Replications -> Publications shows 'No Item's, the little blue hand still appears under the icon next to the previously published database.

So, I'm wondering what has happened? It seems maybe the publication/subscription was only half removed. I've tried running sp_dropsubscription and sp_dropsubscriber on both the published and subscriber, but this hasn't helped.

Any ideas?
 
exec mater..sp_replicationdboption @dbname = <database name>, @optname = 'Publish', @value = 'false'

replcae = <database name> with the dbname of the one with the shared hands...

This will remove the shared hand from the dbname....

which version of SQL server are we talking about here...
 
That stored procedure ran correctly, but the hand is still there. Any more ideas?

The hand on the publishing database is not a huge issue though, it's more of a problem that the subscribing server thinks it's still subscribed. Any idea how to cure that?

Both servers are MS SQL 2000, Service Pack 2 when the replication stuff was done, now both SP3.

Thanks for your reply too...

Cheers,
Matt
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top