Replicate Table

  • I am trying to use a table from my production DB into Development for that I have created a publication on Production using Transactional replication and I used pull subscription on my Dev server. So..when I am doing some modification on my Development table is there any chance for my table on Production to get disturbed? I want my production table to be same AS IS.

  • If you modify any information in your subscriber tables you can cause replication to fail, but you cannot "Push" changes to production .

  • Does it mean that when I use replication, I shud not change my subscriber tables.

  • Changes at the subscriber CAN update the publisher if you've enabled "Immediate Updating". I haven't used it, but the option is there.  Here's the first bit from BOL:

    Immediate Updating

    Immediate updating allows snapshot replication and transactional replication Subscribers to update the replicated data at the Subscriber and send those changes back to the Publisher and to other Subscribers. Immediate updating benefits applications in which snapshot or transactional publications are preferred but occasional updates need to be made at the Subscriber. If using immediate updating, the Publisher and Subscribers must be available and connected.

  • Correct, your replication will fail if the data is not right when that row is updated from the publication.

    The only type of replication you can use if you want to update the subscriber is snapshot replication.

     

Viewing 5 posts - 1 through 4 (of 4 total)

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