Merge replication table changes for on table RRS feed

  • Question

  • We using merge replication in our organasiation , we have 13 subscriber

    I want to update lots of record for one table , but after update this replication have lots of record to upload and download .

    we can use any other way , like snap shot for one table or anything , which not affect my replication ?

    Tuesday, May 14, 2019 6:50 AM

All replies

  • Hi Mayur,


    According to your description, my understanding is that you want to update one of the tables in the replication but you don't want to sync to other subscriber in the replication. If anything is misunderstood, please tell me.


    Three triggers were automatically created when the table was added to Merge replication. These triggers will be used to synchronize when Insert, Update or Delete actions are performed on the table. You only need to modify these three triggers on the publisher (to prevent them from being triggered when the table is modified), and these operations will be synced to all subscribers. After you complete the batch update, modify the trigger back, and it will sync normally.


    You can modify the trigger by following the instructions in the link below:Disable Data Sync for SQL Server Merge Replicated Table via Publisher


    Hope this could help you .

    Best regards,

    Dedmon Dai

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Wednesday, May 15, 2019 6:03 AM
  • Skipping updates by disabling the replication triggers is not good advice. Updating a row which is part of such a change may result in the error message "Unable to synchronize the row because the row was updated by a different process outside of replication."

    It is best to use merge replication to handle this, you may need to use sp_makegeneration to break up the data to be synchronized into 1000 row batches.

    You may find that re-initialization is faster.

    Wednesday, May 15, 2019 1:20 PM