March 18, 2009 at 11:42 pm
I have a database in location A that is to be replicated to location B. Then it needs to be replicated to location C. However the link between A and B is way to slow to allow two subscribers. The only way from C to A is via B.
Given B is a replciation of A, can I simply publish from B and subscribe to B from C?
Thanks
March 19, 2009 at 7:52 am
The answer to your question is "yes", given the information you have supplied. We have to do it because of distribution agent performance problems when running them across a WAN. But I don't fully understand your problem. It seems you need to go from A to B and A to C. Presumably, you can't do this because of the location of the distributor? Then you say the only way FROM C TO A is via B. The start of your post makes it sound like your replication is uni-directional so I don't see why C needs to get to A unless you're running pull subscriptions I suppose and A is your distributor.
March 19, 2009 at 5:53 pm
Appologies if that is unclear.
The link between A and B is slow. The link between B and C is 8 times faster.
I do not want C pulling data via the slow link.
SQL Server C should be able to get the data from B.
That way data only travels once down the slow link.
March 20, 2009 at 4:18 am
Look at Remote Distributor in BOL. We are implementing this technique to reduce bandwidth usage.
Currently we have a number of SQL boxes at a remote site that all take data from the primary site. We are implementing a remote distributor at the remote site that will republish to all SQL boxes at that site. Testing shows we save a load of bandwidth without harming latency.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
March 20, 2009 at 8:16 am
If A is already distributor all is not lost. You can create a PULL Subscription on B and republish B to C.
Now Republishing does have limitations. If a new snapshot needs to be created Or if new tables need to be added there is a lot of maintenance overhead.
* Noel
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply