Such clashes may arise because merge replication does not require a real-time network connection between the publisher and the subscriber, which raises the very real possibility of one server changing data, and another server later changing the very same data to a different value. At any rate, the changes are then synchronized by merge agents that sit on both servers, as well as by a predetermined conflict resolution mechanism in case of clashing data changes. ![]() ![]() In this scenario, it is debatable whether the publisher is strictly the primary server, because other servers can also make changes to the data. ![]() Merge replication is the most complex type of replication because it allows both publisher and subscriber to independently make changes to the database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |