Skip to content

Commit 575dbdd

Browse files
authored
Merge pull request #49971 from anosov1960/patch-33
Update sql-database-geo-replication-overview.md
2 parents 8023960 + f488700 commit 575dbdd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/sql-database/sql-database-geo-replication-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: craigg
77
ms.service: sql-database
88
ms.custom: business continuity
99
ms.topic: conceptual
10-
ms.date: 08/09/2018
10+
ms.date: 08/24/2018
1111
ms.author: sashan
1212
ms.reviewer: carlrab
1313

@@ -124,7 +124,7 @@ For some applications the security rules require that the network access to the
124124

125125
### Using failover groups and virtual network rules
126126

127-
If you are using [Virtual Network service endpoints and rules](sql-database-vnet-service-endpoint-rule-overview.md) to restrict access to your SQL database, be aware that Each Virtual Network service endpoint applies to only one Azure region. The endpoint does not enable other regions to accept communication from the subnet. Therefore, only the client applications deployed in the same region can connect to the primary database. Since the failover results in the SQL client sessions being rerouted to the server in the different (secondary) region, these sessions will fail if originated from a client outside of that region. For that reason, the automatic failover policy cannot be enabled if the participating servers are included in the Virtual Network rules. To support manual failover, follow these steps:
127+
If you are using [Virtual Network service endpoints and rules](sql-database-vnet-service-endpoint-rule-overview.md) to restrict access to your SQL database, be aware that Each Virtual Network service endpoint applies to only one Azure region. The endpoint does not enable other regions to accept communication from the subnet. Therefore, only the client applications deployed in the same region can connect to the primary database. Since the failover results in the SQL client sessions being rerouted to a server in a different (secondary) region, these sessions will fail if originated from a client outside of that region. For that reason, the automatic failover policy cannot be enabled if the participating servers are included in the Virtual Network rules. To support manual failover, follow these steps:
128128

129129
1. Provision the redundant copies of the front end components of your application (web service, virtual machines etc.) in the secondary region
130130
2. Configure the [virtual network rules](sql-database-vnet-service-endpoint-rule-overview.md) individually for primary and secondary server

0 commit comments

Comments
 (0)