Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Which technique uses more network bandwidth:

  1. Log shipping
  2. Transactional Replication

Can some one share any benchmarks for the same ?

What would be the Memory and I/O impact on the Primary server when we use any one of the technique ?


Piyush Patel

share|improve this question
The two techniques do very different things, so I'm not sure it's worth the time comparing them. – spaghettidba Apr 3 '13 at 7:13
Umm, I think that it's not an apple to apple comparison. Because Log shipping sends log backup files, while transactional replication sends commands for transactions (not the log backups) - using system procedures. One is using bandwidth, while the other needs small latency. They both depend on a good network, but on different characteristics. – Marian Apr 3 '13 at 7:15
I would also expect this to be different depending on the DBMS in use. – a_horse_with_no_name Apr 3 '13 at 7:57
Based on the technologies mentioned and the OP's previous questions, I will assume the RDBMS in SQL server. – StanleyJohns Apr 3 '13 at 19:20
up vote 3 down vote accepted

It depends on your workload. As a baseline, use Performance Monitor and log the network counters when not using Log Shipping or Transactional Replication and measure for 1 hour. Then setup Log Shipping and use Performance Monitor to log the network counters for 1 hour. Then setup Transactional Replication and use Peformance Monitor to log the network counters for 1 hour. The network bandwidth that Log Shipping and Transactional Replication consumes is the difference between the collections and the baseline. The same can be done for memory and I/O.

share|improve this answer
Thanks Brandon, that is what exactly i have done. – Piyush Patel Apr 4 '13 at 8:29

I have measure the performance using PerfMonitor and outcome of it as below:

           20 docs ||   20 docs ||   200 docs

Log shipping: 9.88 MB || 10.53 MB || 28.55 MB

Replication: 6.14 MB || 6.80 MB || 17.71 MB

Log Shipping With: 7.86 MB || 9.66 MB || 18.17 MB


So Replication and Log shipping with compression takes almost same network bandwidth. I was measuring these things to know which technique help us to reduce the bandwidth cost from PROD to DR env.


Piyush Patel

share|improve this answer
Why have you accepted your own answer over the recommendation from @BrandonWilliams? – Mark Storey-Smith Apr 6 '13 at 0:29
my bad, i just wanted to upload the image and system did not allow me to do that b'z i did not had a enough points so to gain some i did that. will not do from now onwards !!! – Piyush Patel Apr 8 '13 at 3:47

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.