A typical replication system is based on the
basic primary copy model, in which a primary Replication Server
and a data server are separated across a WAN from replicate Replication
Servers.
Note: This example does not cover the case where primary data is updated
at the replicate database.
Replication System Overview
This Replication System Overview diagram illustrates
how data is replicated from a primary database to replicate databases.
The following actions take place:
- RepAgent reads the primary database log and converts transactions
for tables or stored procedures that are marked for replication
into commands that are sent to Replication Server.The Replication Server stores the transactions in a stable
queue using distributed concurrency control.
- The primary Replication Server:
Determines which Replication Servers manage replicate
databases with subscriptions for the data
The primary Replication Server may have a direct route to
a subscribing Replication Server or an indirect route, with one
or more intermediate Replication Servers in between.
Forwards the transaction to the appropriate replicate
Replication Server, where it is stored in a stable queue
Applies the transaction to any local replicate database
for which there is a subscription for the data
The replicate Replication Server performs one or
both of the following actions: