"Hilary Cotter" wrote:

> Sometimes its hard to drop subscriptions to existing publications where the
> publisher is offline. Its also hard sometimes to kick all your users off
> while you doing the resubscribe, and you will expose yourself to data loss
> here.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> 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
>
>
>
> "Lauren" <Lauren@discussions.microsoft.com> wrote in message
> news:9C0CE6C6-597C-4AF6-BB61-903247EB2A36@microsoft.com...
> > Why does the failback cause difficulties?
> >
> > Lauren
> >
> > "Hilary Cotter" wrote:
> >
> >> that's going to be hard. Failover will be fine. Failback from Server B to
> >> Server A will be difficult.
> >>
> >> --
> >> Hilary Cotter
> >> Director of Text Mining and Database Strategy
> >> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> >>
> >> This posting is my own and doesn't necessarily represent RelevantNoise's
> >> positions, strategies or opinions.
> >>
> >> 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
> >>
> >>
> >>
> >> "Lauren" <Lauren@discussions.microsoft.com> wrote in message
> >> news:C7400EC5-2ED8-473E-A069-E7D160DC2BCE@microsoft.com...
> >> > Kind of, my app is connected to the Express DB which has subscribed to
> >> > replication from Server A. I want to ensure that I can still receive
> >> > replications from B or C when A goes down.
> >> >
> >> > Regards,
> >> > Lauren
> >> >
> >> > "Hilary Cotter" wrote:
> >> >
> >> >> There is no reason you don't continue with your existing setup. It
> >> >> will
> >> >> work. However I assume you have an app currently connected to SQL
> >> >> Server
> >> >> A.
> >> >> When SQL Server A goes down you will have to point this app to SQL
> >> >> Server
> >> >> B.
> >> >> Then you will have to have the SQL Express client resubscribe to SQL
> >> >> Server
> >> >> B.
> >> >>
> >> >> Then when you failback you have to point your app back to SQL Server
> >> >> A,
> >> >> and
> >> >> resubscribe SQL Express to SQL Server A.
> >> >>
> >> >> If you were to cluster you would not have to modify the app or drop
> >> >> the
> >> >> subscription and recreate it each time you failed over.
> >> >>
> >> >> --
> >> >> Hilary Cotter
> >> >> Director of Text Mining and Database Strategy
> >> >> RelevantNOISE.Com - Dedicated to mining blogs for business
> >> >> intelligence.
> >> >>
> >> >> This posting is my own and doesn't necessarily represent
> >> >> RelevantNoise's
> >> >> positions, strategies or opinions.
> >> >>
> >> >> 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
> >> >>
> >> >>
> >> >>
> >> >> "Lauren" <Lauren@discussions.microsoft.com> wrote in message
> >> >> news:3038B03A-ADE9-4F99-81FA-8543DB19CEC2@microsoft.com...
> >> >> > Is there any reason why I couldn't set up 2 servers at each site to
> >> >> > be
> >> >> > both
> >> >> > publisher and subscriber to each other and to the other publishers
> >> >> > in
> >> >> > other
> >> >> > sites or is this a horribly inefficient way of doing things. I
> >> >> > suppose
> >> >> > what I
> >> >> > am asking is is it possible to setup merge replication in a
> >> >> > peer-to-peer
> >> >> > style? Would that be significantly less efficient than peer-to-peer
> >> >> > itself?
> >> >> >
> >> >> > Lauren Eaton
> >> >> >
> >> >> > "Hilary Cotter" wrote:
> >> >> >
> >> >> >> Clustering is probably your best bet. Alternate sync partners will
> >> >> >> be
> >> >> >> supported until the next version. They do have limitations though.
> >> >> >>
> >> >> >> --
> >> >> >> Hilary Cotter
> >> >> >> Director of Text Mining and Database Strategy
> >> >> >> RelevantNOISE.Com - Dedicated to mining blogs for business
> >> >> >> intelligence.
> >> >> >>
> >> >> >> This posting is my own and doesn't necessarily represent
> >> >> >> RelevantNoise's
> >> >> >> positions, strategies or opinions.
> >> >> >>
> >> >> >> 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
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> "Lauren" <Lauren@discussions.microsoft.com> wrote in message
> >> >> >> news:B96733BD-BB07-4196-91C2-A5823E771006@microsoft.com...
> >> >> >> > Hi,
> >> >> >> >
> >> >> >> > After some very helpful advice from this forum, I have set up
> >> >> >> > Merge
> >> >> >> > replication on 2 SQL Server and 1 SQL Express machines. One of
> >> >> >> > the
> >> >> >> > SQL
> >> >> >> > Servers has been configured as the publisher and the other one
> >> >> >> > and
> >> >> >> > the
> >> >> >> > SQL
> >> >> >> > Express as subscribers.
> >> >> >> >
> >> >> >> > This grouping of machines will be repeated throughout our system
> >> >> >> > with
> >> >> >> > each
> >> >> >> > publisher also replicating to the other publishers. I haven't
> >> >> >> > done
> >> >> >> > the
> >> >> >> > second
> >> >> >> > bit yet so I am hoping this makes sense? I assume this would mean
> >> >> >> > setting
> >> >> >> > each publisher up as a subscriber to each other publisher as
> >> >> >> > well -
> >> >> >> > I
> >> >> >> > think I
> >> >> >> > must be on the wrong track here as it sounds very inefficient? I
> >> >> >> > am
> >> >> >> > sure
> >> >> >> > there is a better way?
> >> >> >> >
> >> >> >> > I am also concerned about the fact that each publisher is a
> >> >> >> > single
> >> >> >> > point
> >> >> >> > of
> >> >> >> > failure in this setup. We can't risk that in our system. I know
> >> >> >> > about
> >> >> >> > the
> >> >> >> > alternate sync partner but am a bit concerned about going down
> >> >> >> > that
> >> >> >> > route
> >> >> >> > as
> >> >> >> > it is deprecated and we will likely be moving to new versions
> >> >> >> > whenever
> >> >> >> > they
> >> >> >> > become available for the lifetime of our development project.
> >> >> >> >
> >> >> >> > How do I deal with these issues?
> >> >> >> >
> >> >> >> > Thankyou,
> >> >> >> > Lauren
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>