Re: Merge Replication between sites - Keeping hot backu servers ready
- From: "Javed" <javediqbal98@xxxxxxxxxxx>
- Date: Tue, 4 Oct 2005 16:21:52 +0530
Thanks Paul,
Initially I thought about same keeping A as publisher and rest all
subscribers. But the connectivity between SERVER A and SERVER B (2 MBPS) may
not be enough. There will be lot of other network traffic between office and
can hamper the replication process.
Thank you once again for your prompt help.
Regards
Javed Iqbal
"Paul Ibison" <Paul.Ibison@xxxxxxxxxxxxx> wrote in message
news:O1$4JwMyFHA.2848@xxxxxxxxxxxxxxxxxxxxxxx
> Javed,
> you could set ServerB up as a republisher - subscriber to A and publisher
to
> D. However I think an easier solution would be to have B, C and D as
> subscribers to A if your network speeds can cope with it. In this case, if
B
> goes down, users use D which is regularly synchronized with A. When it
comes
> back on line, A and B are synchronized.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
.
- References:
- Prev by Date: Re: Merge Replication between sites - Keeping hot backu servers ready
- Next by Date: Re: Row filtering - Comparing HOST_NAME() with uniqueidentifier
- Previous by thread: Re: Merge Replication between sites - Keeping hot backu servers ready
- Next by thread: Re: Merge Replication between sites - Keeping hot backu servers ready
- Index(es):
Relevant Pages
|
