THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Argenis Fernandez

Transactional Replication and WAN links

This blog has moved! You can find this content at the following new location:

Published Tuesday, May 31, 2011 9:39 AM by Argenis

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



Robert L Davis said:

Which WAN accelerator are you using? We use Bedrock and just recently got it installed into our datacenters. I don't have metric yet on how it has affected replication.

May 31, 2011 4:40 PM

Argenis said:


The WAN accelerator in our scenario was a Riverbed. I don't have any details on how it was implemented, etc. We treated it as a black box - our go live dates got in the way of working with the Network team and performing proper troubleshooting.

May 31, 2011 5:06 PM

Robert L Davis said:

See, I even got the name wrong. Yes, Riverbed. Not Bedrock. It may be Tuesday, but my brain thinks it is Monday.

May 31, 2011 5:53 PM

Dan said:

Argenis, how did robocopy work for you?  We had to copy a 4TB VLDB and used all sorts of copy utilities and all worked terribly due to limitations on buffered copies.  They would start fast and gradualy slow down to a trickle.

I ended up finding a few articles that recommend using Exchange's ESEUTIL and we then were able to get a sustained 650MB/sec throughput.  Even if lightspeed cut the backup down to a few hundred GB, I'd still recommend using the ESEUTIL for a faster copy.

June 1, 2011 10:18 AM

Argenis said:


robocopy worked pretty well for us. One thing we did to prevent copy problems was to perform the remote copy between two servers that weren't all that busy, and we made sure we always pulled the file - i.e, started the copy at the remote location.

June 1, 2011 11:54 AM

Sankar Reddy said:

To copy (large) files over the network, I am using winRAR to split the file into multiple smaller components and then transfer the smaller chunks. If something fails, I just have to re-start that one smaller file instead of re-trying the complete large file again.

June 1, 2011 12:13 PM

Dave said:

Very interesting thanks. We replicate to subscribers in the same datacentre as well as remote ones, and although we have a fat pipe between the datacentres I've definitely noticed that the remote subscribers take a lot longer to initialize than the local ones.

Is it still possible to initialize from backup when publishing only a subset of data? I wouldn't think so, but haven't had any experience with it.

June 3, 2011 3:11 AM

Argenis said:


In our case the backup files were split. That also helped :)

June 3, 2011 11:46 AM

Argenis said:


Sure you can. You'll just end up with unfiltered data at the subscriber and it would be up to you to _carefully_ deal with that fact.

June 3, 2011 11:51 AM

Kendra Little said:

This is great! I'm adding this to my list of great links on replication.

June 15, 2011 5:59 PM

Will S said:

Hi Argenis. Were your subscriber servers also running Windows/SQL 2008 R2? Just wondering if it's required on both ends to see the TCP/IP improvements. Thanks!

August 18, 2011 1:07 PM

Tom said:

Argenis ,

Can you help me how setup "WAN" Replication (transaction) in SQL Server 2008 R2

I can't find it into the net


August 11, 2012 3:49 AM

Leave a Comment

Privacy Statement