Merge Replication Overview Page 1 of 1
Merge Replication Overview Send Feedback
See Also
Collapse All
Getting Started (Replication) > Overview (Replication) > Types of Replication Overview >
Merge replication, like transactional replication, typically starts with a snapshot of the publication
database objects and data. Subsequent data changes and schema modifications made at the
Publisher and Subscribers are tracked with triggers. The Subscriber synchronizes with the Publisher
when connected to the network and exchanges all rows that have changed between the Publisher and
Subscriber since the last time synchronization occurred.
Merge replication is typically used in server-to-client environments. Merge replication is appropriate
in any of the following situations:
l Multiple Subscribers might update the same data at various times and propagate those changes
to the Publisher and to other Subscribers.
l Subscribers need to receive data, make changes offline, and later synchronize changes with the
Publisher and other Subscribers.
l Each Subscriber requires a different partition of data.
l Conflicts might occur and, when they do, you need the ability to detect and resolve them.
l The application requires net data change rather than access to intermediate data states. For
example, if a row changes five times at a Subscriber before it synchronizes with a Publisher, the
row will change only once at the Publisher to reflect the net data change (that is, the fifth value).
Merge replication allows various sites to work autonomously and later merge updates into a single,
uniform result. Because updates are made at more than one node, the same data may have been
updated by the Publisher and by more than one Subscriber. Therefore, conflicts can occur when
updates are merged and merge replication provides a number of ways to handle conflicts.
For information about implementing merge replication, see Designing and Implementing
(Replication).
For information about common scenarios that involve merge replication, see Replicating Data
Between a Server and Clients.
See Also
Concepts
How Merge Replication Works
Physical Architecture (Replication)
Other Resources
Designing and Implementing (Replication)
Help and Information
Getting SQL Server 2008 R2 Assistance
Documentation Feedback
Microsoft values your feedback. To rate this topic and send feedback about this topic to the
documentation team, click a rating, and then click Send Feedback. For assistance with support
issues, refer to the technical support information included with the product.
Poor 1 2 3 4 5 Outstanding
To e-mail your feedback to Microsoft, click here: Send Feedback
© 2010 Microsoft Corporation. All rights reserved.
ms-help://[Link].v10/[Link]/s10rp_0evalplan/html/ff87c368-4c00-... 14/7/2016