Merge replication 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.
Stats
created |
4 months ago |
viewed |
3 times |
active |
4 months ago |
editors |
1 |
Recent Hot Answers
Estimated versus actual query plan with function callsWorking Around Filtering Problems in Merge Replication
The issue of sp_MScheckIsPubOfSub stored procedure
SQL Server Merge Replication, Agent Batch Size
Table with identity column in merge replication
more »
Related Tags
sql-server × 59replication × 35
sql-server-2008 × 15
sql-server-2012 × 6
sql-server-2005 × 5
sql-server-2008-r2 × 4
sql × 2
sql-server-ce × 2
mirroring × 2
backup × 2
snapshot
scalability
deadlock
query-plan
functions
transactional-replication
log
ms-access
identity
sql-server-compact
mysql
ddl
sql-server-2000
restore