November 29, 2007 at 3:56 pm
Dear all, I am an "experienced" Sql developer/DBA (2000-2005) but I have very little experience of Replication.
I have just been asked to give a hand at a Production system (Sql 2000) which uses Replication.
There are 2 snapshot publications and 3 Transactional publications with Push subscriptions.
The Publisher is also the Distributor.
From what I gather, there was some problem (probably hardware) on the Publisher about 17 days ago.
If I watch on the Subscriber side, the state of the 3 subscriptions is "In Progress" but I am being told that nothing seems replicated.
If I watch on the Publisher/Distributor side, it looks like the Push Subscriptions had an "expiration" of 336 hours (which seems to be the default) which would have expired a couple of days ago.
Question:
In order to restart the (failed) subscriptions, I suppose I'll have to
1) delete the 3 (transactional) subscriptions on the subscriber
2) recreate them as new Push subscriptions on the Publisher/Distributor
Is this correct?
I am "slightly" nervous as this is a production system...
Thanks
Eric
🙂
November 30, 2007 at 11:14 am
You don't need to drop & recreate - on publisher, right click on subscription and select re-init.
YOu will need to run you snapshot agent for this pub. Don't run in middle of day if - pub is heavy trans and/or there are many tables (or large tables) in your publication sever blocking on pub can result.
Best to do after hours since never done before. Keep in mind you will need to visit the tables on your subscriber - they most likely will get dropped & recreated. Visit perms, constraints etc if needed.
ChrisB MCDBA
MSSQLConsulting.com
Chris Becker bcsdata.net
December 3, 2007 at 11:08 am
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply