Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


2008 R2 Transactional Replication

2008 R2 Transactional Replication

2008 R2 Transactional Replication

When setting up replication, does the publisher make an initial backup and then restore on the subscriber as in Log Shipping? If not, then what happens if you have the two dbs matching on Tuesday, but don't get replication setup until Friday? What happens to everything that happened between those days to the publisher but not the subscriber?


RE: 2008 R2 Transactional Replication

You can set up transactional replication in two ways. In one way you declare that the subscriber already has the data, and a snapshot is not necessary. This is usually used for topologies that include very large sets of data, or may have limited network bandwidth to push the initial snapshot through. If you take this option, you will need to settle how the initial snapshot makes its way to the subscriber. i suspect it will involve at least a few transaction log backups, and if you have high update volumes, maybe even a short bit of downtime.

The other option (the default option, actually) is to let the snapshot agent bulk copy the data from the publisher to the subscriber. I would advise you to try that out on tables of a few sizes to see what the limits of your setup may be.

RE: 2008 R2 Transactional Replication

That makes sense, sounds like the default acts like Log Shipping in the initial setup. Thanks!

RE: 2008 R2 Transactional Replication

To be clear, the snapshot job will only copy individual tables. If the subscriber database has other data in it (tables that are not published/subscribed), those tables will not be affected. With log shipping, the entire database is wiped out.

RE: 2008 R2 Transactional Replication

Perfect, thank you!


Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close