Wednesday, March 28, 2012

Merge Replication, going back to primary Publiser

Hello this is a simple question. I have merge replication and I followed the
following steps in
http://support.microsoft.com/default...b;en-us;321176 to set this
up. We had to turn off the PublisherA server because of the hurricanes and
the PublisherB and SubscriberA, B and C are being replicated between
themselves. Now I have PublisherA back and on-line and the replication is
stopped in PubA. To have PubA back as primary publisher again, what do I
need to do? just start synch from PublisherA and the data will be replicated
from PubA to PubB and Subscribers A,B and C and viceversa? or do I need to
do some aditional step?
Thanks in advance
Jennyfer
change the agents to point back to publisher A. remove the -SyncToAlternate
parameter.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jennyfer Barco" <pdwhitt@.nospam.wdsinc.com> wrote in message
news:OuvlPsX4FHA.2552@.TK2MSFTNGP10.phx.gbl...
> Hello this is a simple question. I have merge replication and I followed
the
> following steps in
> http://support.microsoft.com/default...b;en-us;321176 to set this
> up. We had to turn off the PublisherA server because of the hurricanes and
> the PublisherB and SubscriberA, B and C are being replicated between
> themselves. Now I have PublisherA back and on-line and the replication is
> stopped in PubA. To have PubA back as primary publisher again, what do I
> need to do? just start synch from PublisherA and the data will be
replicated
> from PubA to PubB and Subscribers A,B and C and viceversa? or do I need to
> do some aditional step?
> Thanks in advance
> Jennyfer
>
|||When doing this I lost many records in some tables and some tables where
almost gone in the publisher A. Now I'm bringing the missing record from
Publisher B and it takes to much time because when inserting these records
in publisher A it's trying to update them in Publisher B and subscribers.
How can I improve this, at this rate it will take me weeks to have the
databases on sync. They're thousands of records gone and why did this
happen, he just deleted important records.
thanks in advance
Jennyfer
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:Oj9rRxb4FHA.3444@.tk2msftngp13.phx.gbl...
> change the agents to point back to publisher A. remove
> the -SyncToAlternate
> parameter.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Jennyfer Barco" <pdwhitt@.nospam.wdsinc.com> wrote in message
> news:OuvlPsX4FHA.2552@.TK2MSFTNGP10.phx.gbl...
> the
> replicated
>
|||Hello I'm sending this again since I didn't have any answer. My important
question is why thousands of records are gone? Why when switching I lost
many records? And 2 small tables that have around 500 records and are being
replicated and are not transactional records are gone too. They were gone
when trying to swicth, and they had records and those are very important
tables like stores and users tables.
Thanks
"Jennyfer Barco" <pdwhitt@.nospam.wdsinc.com> wrote in message
news:uGjsuKf5FHA.3588@.TK2MSFTNGP15.phx.gbl...
> When doing this I lost many records in some tables and some tables where
> almost gone in the publisher A. Now I'm bringing the missing record from
> Publisher B and it takes to much time because when inserting these records
> in publisher A it's trying to update them in Publisher B and subscribers.
> How can I improve this, at this rate it will take me weeks to have the
> databases on sync. They're thousands of records gone and why did this
> happen, he just deleted important records.
> thanks in advance
> Jennyfer
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:Oj9rRxb4FHA.3444@.tk2msftngp13.phx.gbl...
>

No comments:

Post a Comment