This article shows how to configure SQL Server replication for the database in SQL Server Always On Availability Group
In the earlier article (see TOC at the bottom), we explored how you can add the publisher and subscriber database in a high availability configuration using SQL Server Always On Availability Groups. It used a remote distributor for transactional replication.
Suppose the publisher and subscriber databases are on [SQLAG1\INST1] node, and failover happens to the node [SQLAG2\INST2]. In this case, the transactional replication works fine without any issues. It provided high resilience for the publisher and subscriber database.
What about the distribution database? Can we add it to the availability group? In this article, let’s explore the steps required for the distribution database AG.
We can add the replication distribution database in the availability group for high availability starting from SQL Server 2017 CU6 and SQL Server 2016 SP2-CU3. It requires special considerations for adding the distribution database.
In this article, we use the following environment.
Existing AG configuration:
We configure the distribution database in a new availability group on the following replicas.
For this article, we use a standalone instance for the publisher and subscriber.
Publisher and Subscriber: SQLNode3\INST3
Therefore, the overall configuration in terms of the SQL Server replication topology is as below.:
You can use the previous articles in the series to prepare a similar environment.
Note: You can find the script attached at the bottom of the article.
This article gives an overview of SQL Server Always On Availability Group features. SQL Server Always On Availability Groups create a group of databases that fails over together in case the primary replica is unavailable.
This article shows how to configure SQL Server replication for the database in SQL Server Always On Availability Groups
This article gives an overview of Configuring Managed Service Accounts for SQL Server Always On Availability Groups.
SQL Server 2016 provides a new feature Distributed Availability Group for disaster recovery purposes. It is a particular type of availability group that helps access the multiple failover clusters. In this article’s series, we configured a traditional Always On group. It has the following requirements.
This article configures SQL Server Always On Availability Groups on the domain independent Windows Failover Clusters. In the previous article, Deploy a domain-independent Windows Failover Cluster for SQL Server Always On Availability Groups, we learned the new capability in Windows Server 2016 to configure a domain-independent Windows failover cluster.