July 26, 2005 at 1:24 pm
Hi all,
I'm new to this one.
Just want to make sure the purpose of this type of replication is NOT to traverse the Subscriber from Publisher to Publisher, but to propogate to both Publishers if the Subscriber is updated
1. Create publication on Pub1, in replication Properties->Synch Partners, check Allow Subscribers.
2. Push the subscribtion from Pub1 to the Subscriber, then from Pub2 to the same Subscriber.
3. Edit Merger Agent job on both Publishers. Add –SyncToAlternate to the Run Agent step.
The updates from Pub1 will propagate to Subscriber, but not to Pub2
The updates from Pub2 will propagate to Subscriber, but not to Pub1
The updates from Subscriber will propagate to Pub1 and to Pub2
Thanks
July 27, 2005 at 4:32 am
sort of. Alternate sync partners are standby merge replication publishers which the subscriber can sync with for short amounts of time before the original publisher comes back online. The subscriber will be synchronizing with the publisher and the publisher will be synchronizing with the alt sync publisher. The subscriber will never synchronize with the alt sync partner unless you manually configure it to do so.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
July 27, 2005 at 5:04 am
thanks Hilary,
So to simulate the failover is it enouph to disable publication on the mail publisher?
July 28, 2005 at 4:47 am
no, you have to visit each subscriber and point them to the alt sync publisher.
follow these instructions
http://support.microsoft.com/default.aspx?scid=kb;en-us;321176
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply