Skip to content

Commit d24f5e9

Browse files
authored
Merge pull request #92693 from anosov1960/patch-93
Update sql-database-auto-failover-group.md
2 parents 7325750 + 747b3ea commit d24f5e9

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/sql-database/sql-database-auto-failover-group.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.topic: conceptual
1010
author: anosov1960
1111
ms.author: sashan
1212
ms.reviewer: mathoma, carlrab
13-
ms.date: 10/09/2019
13+
ms.date: 10/21/2019
1414
---
1515

1616
# Use auto-failover groups to enable transparent and coordinated failover of multiple databases
@@ -143,6 +143,9 @@ When designing a service with business continuity in mind, follow these general
143143
- **Use one or several failover groups to manage failover of multiple databases**
144144

145145
One or many failover groups can be created between two servers in different regions (primary and secondary servers). Each group can include one or several databases that are recovered as a unit in case all or some primary databases become unavailable due to an outage in the primary region. The failover group creates geo-secondary database with the same service objective as the primary. If you add an existing geo-replication relationship to the failover group, make sure the geo-secondary is configured with the same service tier and compute size as the primary.
146+
147+
> [!IMPORTANT]
148+
> Creating failover groups between two servers in different subscriptions is not currently supported for single databases and elastic pools.
146149
147150
- **Use read-write listener for OLTP workload**
148151

0 commit comments

Comments
 (0)