A variation of the existing AOAG feature that connect AGs in two or more clusters. Distributed Availability Groups are a new feature in SQL Server 2016.
Questions tagged [distributed-availability-groups]
69 questions
22
votes
3 answers
SQL Server Distributed Availability Group databases not syncing after a server reboot
We're getting ready to perform a large upgrade on our SQL Servers and are noticing some unusual behavior with Distributed Availability Groups that I'm trying to resolve before moving forward.
Last month, I upgraded a remote secondary server from…
Taryn
- 9,746
- 4
- 48
- 74
11
votes
3 answers
Distributed Availability Group with Manual Seeding
I am looking for a step by step walk through of how to setup a distributed availability group with manual seeding. I can get the automatic seeding working but when I try to manually seed I cannot get the secondary database into the AG on the…
Alf47
- 981
- 1
- 9
- 22
7
votes
3 answers
Cannot remove Database from Distributed AlwaysOn Group on Secondary Windows Cluster
We have Distributed AG across two windows clusters.
Clus01 - Has an AG set up with no DB inside it (AG1)
Clus02 - Has an AG set up with no DB inside it (AG2)
Clus01 - Has a DistAG set up with AG1 (primary) and AG2 (secondary)
We
Joined Clus02…
DJSQL
- 73
- 1
- 1
- 3
6
votes
1 answer
Distributed Availability Groups refusing to resync my FILESTREAM database with SUSPEND_FROM_CAPTURE
My home lab setup consists of four servers running in HyperV across two physical hosts. The SQL Server instances are SQLAG101, SQLAG102, SQLAG201, and SQLAG202.
SQLAG101 and SQLAG102 are members of the SQLAG100 Availability Group, and are on the…
Hannah Vernon
- 70,928
- 22
- 177
- 323
5
votes
2 answers
Distributed Availability Group Direct Seeding FAILED, failure_state SQL Error, failure_state 2
We just started setting up Distributed Availability groups to replicate our production databases into a new reporting cluster. The first availability group that we setup for replication worked great without any issues, however when we then moved on…
Greg Bray
- 1,053
- 3
- 13
- 20
4
votes
2 answers
MS SQL 2017 cluster: impact of disabling distributed transactions for an availability group
A company is having a Microsoft SQL Server 2017 Enterprise cluster (RTM-GDR, 64-bit, 14.0.2027.2, KB4505224) consisting of one Availability Group (AG) with two servers, a primary and a secondary.
A closed source application used by this company…
Arthur Borsboom
- 143
- 3
4
votes
1 answer
Distributed AG on SQL Server 2017 Standard Edition?
Can I configure Distributed AG with SQL Server 2017 Standard Edition?
Luis Agustin Azario
- 43
- 3
4
votes
1 answer
Mixing SQL Server 2016 and 2017 in a distributed availability group
I have an old Availability Group made up of 2 SQLServer 2016 instances (2 Windows 2016 servers in WSFC)
I also have 2 new SQLServer 2017 instances (2 Windows Server 2016) that I originally wanted to join to the 2016 AG.
This is a 0 downtime…
Blablas
- 43
- 6
3
votes
2 answers
function to check whether the current server is involved in an availability group and if so, whether it is the primary
I used to have 2 servers on an availability group, but there was a problem with one of them servers involved,while patching, and to make a long story short I removed all the databases from the availability group.
The way I managed execution of jobs…
Marcello Miorelli
- 17,274
- 53
- 180
- 320
3
votes
1 answer
Orphaned Availability Group Name
So I was creating a distributed availability group and noticed I wanted to change the name of the AG so I tried to run DROP AVAILABILITY GROUP. But it was already seeding and was just stuck in "Cancelling" status. So I restarted the SQL Service to…
GoldenDBA
- 51
- 2
3
votes
2 answers
SQL Server - Is there a limit to the number of Distributed Availability Groups that a primary replica can participate in?
The documentation has diagrams with availability groups taking part in multiple Distributed Availability Groups (AG 1, AG 2 and AG 3) take part in Distibuted AG1 ([AG 1, AG 2]) and Distributed AG2 ([AG 2, AG…
Marksl
- 175
- 7
2
votes
1 answer
Failover of of SQL Server Distributed Availability Group
Following the steps in Manual Failover of SQL Server DAG
To verify if both Availability Groups are ready for failover, use the T-SQL query below, running in SQLCMD Mode:
:CONNECT TDPRD071
SELECT ag.name, drs.database_id, db_name(drs.database_id)…
PTL_SQL
- 405
- 4
- 11
- 27
2
votes
3 answers
What affects log_send_rate in Normal or Distributed AG other than OS resources?
I am observing low log_send_rate in my distributed AG setup.
I understand that AG uses log stream and so I assume it should not have anything to do with data, but I was wondering if this has anything to do with data it is transmitting also and not…
GAURAV RATHOD
- 186
- 1
- 13
2
votes
1 answer
SQL Server Distributed Availability Group databases not syncing after a Global Primary Replica Failover
SQL Server Distributed Availability Group Environment
AG1 => Node1 (AG1-Global Primary) and Node2 (AG1 - Secondary Replica)
AG2 => Node3 (AG2-Forwarder) and Node4 (AG2 - Secondary Replica)
DAGE => Distributed Availability Group Environment
DAGE…
HvyOnEz Solid-Ground
- 31
- 4
2
votes
1 answer
Remove database from Distributed Availability Group replica AG ONLY!
all!
I have an existing always on availability group on-prem and last week created a second one in AWS. After that, I created a distributed availability group with on-prem as primary and AWS as the replica AG.
Being new to SQL Server, I configured…
calmkza
- 21
- 1