Skip to content

Commit e368d45

Browse files
MladjoAMladjoA
committed
Incorporating the GeoDR team feedback
1 parent 13f91b8 commit e368d45

2 files changed

Lines changed: 5 additions & 5 deletions

File tree

‎azure-sql/managed-instance/auto-failover-group-configure-sql-mi.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -30,12 +30,12 @@ This article teaches you how to configure an [auto-failover group](auto-failover
3030
Consider the following prerequisites:
3131

3232
- The secondary managed instance must be empty that is, contain no user databases.
33-
- The two instances of SQL Managed Instance need to be the same service tier, and have the same storage size.
34-
- The IP address range of the subnet hosting the primary instance must not overlap with IP address range of the subnet hosting the secondary instance.
35-
- Network Security Groups (NSG) rules on subnet hosting instance must have port 5022 and the port range 11000-11999 open inbound and outbound for connections from the subnet hosting the other managed instance.
33+
- The two instances of SQL Managed Instance need to be the same service tier, and have the same storage size. While not reqiured, it's strongly recommended that two instances have equal compute size, to make sure that secondary instance can sustainably process the changes being replicated from the primary instance, including the periods of peak activity.
34+
- The IP address range(s) of the virtual network hosting the primary instance must not overlap with IP address range(s) of the virtual network hosting the secondary instance.
35+
- Network Security Groups (NSG) rules on subnet hosting instance must have port 5022 and the port range 11000-11999 open inbound and outbound for connections from and to the subnet hosting the other managed instance. This applies to both subnets, hosting primary and secondary instance.
3636
- The secondary SQL Managed Instance is configured during its creation with the correct DNS zone ID. It's accomplished by passing the primary instance's zone ID as the value of DnsZonePartner parameter when creating the secondary instance. If not passed as a parameter, the zone ID is generated as a random string when the first instance is created in each VNet and the same ID is assigned to all other instances in the same subnet. Once assigned, the DNS zone can't be modified.
3737
- The collation and time zone of the secondary managed instance must match that of the primary managed instance.
38-
- Managed instances should be deployed in [paired regions](/azure/availability-zones/cross-region-replication-azure) for performance reasons. Managed instances residing in geo-paired regions have much better replication speed compared to unpaired regions.
38+
- Managed instances should be deployed in [paired regions](/azure/availability-zones/cross-region-replication-azure) for performance reasons. Managed instances residing in geo-paired regions benefit from significantly higher geo-replication speed compared to unpaired regions.
3939

4040
## Enabling connectivity between the instances
4141

‎azure-sql/managed-instance/auto-failover-group-sql-mi.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ The failover group will manage geo-failover of all databases on the primary mana
139139
140140
## <a name="using-read-write-listener-for-oltp-workload"></a> Use the read-write listener (primary MI)
141141

142-
For read-write workloads, use `<fog-name>.zone_id.database.windows.net` as the server name. Connections will be automatically directed to the primary. This name doesn't change after failover. The geo-failover involves updating the DNS record, so the client connections are redirected to the new primary only after the client DNS cache is refreshed. Because the secondary instance shares the DNS zone with the primary, the client application will be able to reconnect to it using the same server-side SAN certificate. The read-write listener and read-only listener cannot be reached via the [public endpoint for managed instance](public-endpoint-configure.md).
142+
For read-write workloads, use `<fog-name>.zone_id.database.windows.net` as the server name. Connections will be automatically directed to the primary. This name doesn't change after failover. The geo-failover involves updating the DNS record, so the new client connections are routed to the new primary only after the client DNS cache is refreshed. Because the secondary instance shares the DNS zone with the primary, the client application will be able to reconnect to it using the same server-side SAN certificate. The existing client connections need to be terminated and then recreated to be routed to the new primary. The read-write listener and read-only listener cannot be reached via the [public endpoint for managed instance](public-endpoint-configure.md).
143143

144144
## <a name="using-read-only-listener-to-connect-to-the-secondary-instance"></a> Use the read-only listener (secondary MI)
145145

0 commit comments

Comments
 (0)