Replication model | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Replication model

Which replication model(Merge,snapshot,transactional) will be suitable for a web hosting company ,which has 8 branches spread accross the subcontinents
Hi aaronsandy,
From BOL:
The method you choose depends on your replication topology and the needs of your application and its users Use merge replication when . . . Replicated data is read and updated at the Subscriber.
Subscriber and Publisher are only occasionally connected.
Conflicts caused by multiple updates to the same data are handled and resolved.
You need updates to be propagated on a row-by-row basis, and conflicts to be evaluated and resolved at the row level. Use snapshot replication or transactional replication with immediate updating or queued updating when . . .
Replicated data is mostly read-only at the Subscriber.
Subscriber, Distributor, and Publisher are connected most of the time, but this is not necessary for queued updating subscriptions.
Conflicts caused by multiple updates to the same data are infrequent.
You need updates to be propagated on a transaction basis, and conflicts to be evaluated and resolved on a transaction basis (the entire transaction is either committed or rolled back).
]]>