Specifying immediate updates

You have the option to utilize a tight or loose consistency model. In a tight consistency model, transactions are applied at multiple locations at once. If all transactions have no errors, the transaction is commited simultaneously at all sites. In a loose consistency model, the transactions are committed at the publisher. They are then sent out to each of the subscribing sites. If conflicts occur, they can be handled on a case by case basis. However, the transaction is still committed at the publisher and does not roll back if there is a failure at a subscriber. Tight consistency is always desirable, because it ensures that all databases will always contain the same data. This consistency comes at a significant price. A tight consistency model can cause transactions to be held open for a significant amount of time while communication occurs between the publisher and subscriber. This means that an application must wait much longer than usual before it can be notified whether the modification request succeeded or failed. For this reason, selecting the option for not allowing immediate updating of subscribers is the most common.

Replication Primer 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40