Transactional replication typically starts with a snapshot of the publication database objects and data. As soon as the initial snapshot is taken, subsequent data changes and schema modifications made at the Publisher are usually delivered to the Subscriber as they occur (in near real time). The data changes are applied to the Subscriber in the same order and within the same transaction boundaries as they occurred at the Publisher; therefore, within a publication, transactional consistency is guaranteed.. GeoPITS brings you the comprehensive details of Transactional replication's support in different versions & editions of SQL Server.
| Version | Enterprise | Standard | Web | Express (Adv.) | Express |
|---|---|---|---|---|---|
| Version v2019 | Yes | Yes | Yes (Subscriber only) | Yes (Subscriber only) | Yes (Subscriber only) |
| Version v2017 | Yes | Yes | Yes (Subscriber only) | Yes (Subscriber only) | Yes (Subscriber only) |
| Version v2016 | Yes | Yes | Yes (Subscriber only) | Yes (Subscriber only) | Yes (Subscriber only) |
| Version v2014 | Yes | Yes | Yes (Subscriber only) | Yes (Subscriber only) | |
| Version v2012 | Subscriber only | Subscriber only | Subscriber only |
Transactional replication typically starts with a snapshot of the publication database objects and data. As soon as the initial snapshot is taken, subsequent data changes and schema modifications made at the Publisher are usually delivered to the Subscriber as they occur (in near real time). The data changes are applied to the Subscriber in the same order and within the same transaction boundaries as they occurred at the Publisher; therefore, within a publication, transactional consistency is guaranteed.
You can find more details about this version here
Back to all features