Freigeben über

Transactional Replication and Always On Availability Groups Support Update

  • Artikel

In the past, we have received multiple requests from customers for supporting transactional replication republishers in an Always On Availability Group configuration. We are pleased to announce that starting from SQL Server 2016, transactional replication republisher is supported in an Always On Availability Group configuration. See “Replication, Change Tracking, Change Data Capture, and Always On Availability Groups (SQL Server)” for more details.The table below shows the supported combinations of replication on Always On Availability Groups.

  Publisher Distributor Subscriber
Transactional Replication YesNote: Does not include support for bi-directional and reciprocal transactional replication No Yes

Transactional replication subscribers do not need special handling while participating in Always On Availability Groups. Subscribers must be running SQL Server 2012 or later to participate in an availability group. For more information, see Replication Subscribers and Always On Availability Groups (SQL Server)

--

Amit Banerjee

@banerjeeamit

Comments

  • Anonymous
    August 31, 2016
    Thanks Amit for sharing. another cool enhancements in 2016
  • Anonymous
    April 17, 2017
    Hi Amit,you have mentioned the transaction replication republisher is supported in SQL Server Always On configuration, did you mean that following configuration is possible in SQL Server 2016:Server 1 - Instance 1 - DB1 - PublisherServer 2 - Instance 2 - DB1 - Subscriber - also acting as republisher for Server 3 Server 3 - Instance 3 - DB1 - Subscriber for Server 3In above configuration we can have Server2/Instance2/DB1 in SQL Server Always On Configuration ?Also, can you please send any case studies related to the above ?
    • Anonymous
      May 10, 2017
      Re-publisher in this context means a database which is also a subscriber and a publisher. In your example above, you can have Server 2/Instance 2/DB1 as part of an Always On setup. This is standard Replication configuration and no special handling is required for configuring Availability Groups.