Skip to content

Commit 5780ff6

Browse files
authored
Update migrate-sql-server-failover-cluster.md
fixed typo (SQL Server Always On Failover Customer Instance > SQL Server Always On Failover Cluster Instance)
1 parent 2561795 commit 5780ff6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-vmware/migrate-sql-server-failover-cluster.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ The following table indicates the estimated downtime for migration of each SQL S
5757
|:---|:-----|:-----|
5858
| **SQL Server standalone instance** | Low | Migration is done using VMware vMotion, the database is available during migration time, but it isn't recommended to commit any critical data during it. |
5959
| **SQL Server Always On Availability Group** | Low | The primary replica will always be available during the migration of the first secondary replica and the secondary replica will become the primary after the initial failover to Azure. |
60-
| **SQL Server Always On Failover Customer Instance** | High | All nodes of the cluster are shut down and migrated using VMware HCX Cold Migration. Downtime duration depends upon database size and private network speed to Azure cloud. |
60+
| **SQL Server Always On Failover Cluster Instance** | High | All nodes of the cluster are shut down and migrated using VMware HCX Cold Migration. Downtime duration depends upon database size and private network speed to Azure cloud. |
6161

6262
## Windows Server Failover Cluster quorum considerations
6363

0 commit comments

Comments
 (0)