Snapshot Replication and Merge Replication

Question

Do we have to publish the article every time if there is changes to the article or we just need to publish it once and the system will automatically replicate the changes in snapshot replication?

Is there any way that we can stop or disallow subscriber from updating data into the publisher in a merge replication?

Answer 1

Hi @Cindy See ,

> Do we have to publish the article every time if there is changes to the article or we just need to publish it once and the system will automatically replicate the changes in snapshot replication? You do not need to publish the article every time. After a publication has been created, most publication and article properties can be changed, but some require that the snapshot be regenerated and/or subscriptions be reinitialized. Please refer this MS document: Change Publication and Article Properties. > Is there any way that we can stop or disallow subscriber from updating data into the publisher in a merge replication? Isn't the syncing of subscribers to publishers a feature of merged replication? If you have the option, you can choose another replication. I found this post. It mentions that you can add a row filter. Like this WHERE HOST_NAME() ! = 'Server A' But I don't have the environment to reproduce this method now. The best advice is still that you can deploy another replication.

Best regards, Seeya

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.