Skip to content

Commit ed187e2

Browse files
authored
Merge pull request #92911 from anosov1960/patch-94
Update sql-database-auto-failover-group.md
2 parents 1961462 + 123bac3 commit ed187e2

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/21/2019
13+
ms.date: 10/22/2019
1414
---
1515

1616
# Use auto-failover groups to enable transparent and coordinated failover of multiple databases
@@ -84,6 +84,9 @@ To achieve real business continuity, adding database redundancy between datacent
8484
- **Automatic failover policy**
8585

8686
By default, a failover group is configured with an automatic failover policy. The SQL Database service triggers failover after the failure is detected and the grace period has expired. The system must verify that the outage cannot be mitigated by the built-in [high availability infrastructure of the SQL Database service](sql-database-high-availability.md) due to the scale of the impact. If you want to control the failover workflow from the application, you can turn off automatic failover.
87+
88+
> [!NOTE]
89+
> Because verification of the scale of the outage and how quickly it can be mitigated involves human actions by the operations team, the grace period cannot be set below one hour. This limitation applies to all databases in the failover group regardless of their data synchronization state.
8790
8891
- **Read-only failover policy**
8992

0 commit comments

Comments
 (0)