Skip to content

Commit e5bf6d3

Browse files
author
Ian Whyte
committed
avs cleanup
1 parent b38aedd commit e5bf6d3

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.custom: engagement-fy23
1111

1212
# Migrate a SQL Server standalone instance to Azure VMware Solution
1313

14-
In this article, you learn how to migrate a SQL Server Standalone to Azure VMware Solution.
14+
In this article, you learn how to migrate a SQL Server standalone instance to Azure VMware Solution.
1515

1616
When migrating a SQL Server standalone instance to Azure VMware Solution, VMware HCX offers two migration profiles:
1717

@@ -39,7 +39,7 @@ This scenario was validated using the following editions and configurations:
3939
- Remove all cluster node VMs from any Distributed Resource Scheduler (DRS) groups and rules.
4040

4141
- Configure VMware HCX between your on-premises datacenter and the Azure VMware Solution private cloud that runs the migrated workloads. For more information about configuring VMware HCX, see [Azure VMware Solution documentation](install-vmware-hcx.md).
42-
- Ensure that all the network segments in use by the SQL Server are extended into your Azure VMware Solution private cloud. To verify this step in the procedure, see [Configure VMware HCX network extension](configure-hcx-network-extension.md).
42+
- Ensure that all the network segments in use by the SQL Server and workloads using it are extended into your Azure VMware Solution private cloud. To verify this step in the process, see [Configure VMware HCX network extension](configure-hcx-network-extension.md).
4343

4444
Either VMware HCX over VPN or ExpressRoute connectivity can be used as the networking configuration for the migration.
4545

@@ -52,7 +52,7 @@ Further downtime considerations are discussed in the next section.
5252
## Downtime considerations
5353

5454
Downtime during a migration depends on the size of the database to be migrated and the speed of the private network connection to Azure cloud.
55-
Migration of the Microsoft SQL Server Standalone instance using the VMware HCX vMotion mechanism is intended to minimize the solution downtime, however we still recommend the migration take place during off-peak hours with a pre-approved change window.
55+
Migration of a SQL Server standalone instance using the VMware HCX vMotion mechanism is intended to minimize the solution downtime, however we still recommend the migration take place during off-peak hours within an pre-approved change window.
5656

5757
This table indicates the estimated downtime for migration of each SQL Server topology.
5858

articles/azure-vmware/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -191,11 +191,11 @@ items:
191191
href: deploy-vsan-stretched-clusters.md
192192
- name: Migrate Microsoft SQL Server workloads
193193
items:
194-
- name: Migrate Microsoft SQL Server Standalone to Azure VMware Solution
194+
- name: Migrate a SQL Server standalone instance to Azure VMware Solution
195195
href: migrate-sql-server-standalone-cluster.md
196196
- name: Migrate SQL Server failover cluster to Azure VMware Solution
197197
href: migrate-sql-server-failover-cluster.md
198-
- name: Migrate Microsoft SQL Server Always-On cluster to Azure VMware Solution
198+
- name: Migrate Microsoft SQL Server Always-On Availability Group to Azure VMware Solution
199199
href: migrate-sql-server-always-on-availability-group.md
200200
- name: Move resources
201201
items:

0 commit comments

Comments
 (0)