Caveats when Replicating?

  • Never having replicated anything before, I'm wondering if there are any caveats to keep in mind. For example, I think I heard somewhere that using identity as PK can cause problems when replicating. We are considering transactional(?) replication to move data incrementally from our live server to a reporting system. Any comments would be appreciated.

  • For read only subscribers it's cake. If you'll have updating subscribers (transactional or merge) SQL will still handle the idents for you by issuing ranges to each subscriber. Biggest caveat is that you're limited to the changes you can make once you publish a table. It's still manageable, just another layer to deal with. I'd definitely recommend that you do some test runs to get comfortable with everything first. Replication is very very useful, I use it a lot with great results.

    Andy

    http://www.sqlservercentral.com/columnists/awarren/

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply