When data is updated at a Subscriber, it is first propagated to the Publisher and then propagated to other Subscribers. If immediate updating is used, the changes are propagated immediately using the two-phase commit protocol. If queued updating is used, the changes are stored in a queue; the queued transactions are then applied asynchronously at the Publisher whenever network connectivity is available. Because the updates are propagated asynchronously to the Publisher,. GeoPITS brings you the comprehensive details of Transactional replication updateable subscription's support in different versions & editions of SQL Server.
| Version | Enterprise | Standard | Web | Express (Adv.) | Express |
|---|---|---|---|---|---|
| Version v2019 | Yes | Yes | |||
| Version v2017 | Yes | Yes | |||
| Version v2016 | Yes | Yes | |||
| Version v2014 | Yes | ||||
| Version v2012 |
When data is updated at a Subscriber, it is first propagated to the Publisher and then propagated to other Subscribers. If immediate updating is used, the changes are propagated immediately using the two-phase commit protocol. If queued updating is used, the changes are stored in a queue; the queued transactions are then applied asynchronously at the Publisher whenever network connectivity is available. Because the updates are propagated asynchronously to the Publisher,
You can find more details about this version here
Back to all features