more MW input

Author: Whyte

articles/azure-vmware/migrate-sql-server-always-on-availability-group.md

@@ -14,6 +14,8 @@ In this article, you learn how to migrate a SQL Server Always On Availability Gr
 
 :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-architecture.png" alt-text="Diagram showing the architecture of Always On SQL Server for  Azure VMware Solution." border="false" lightbox="media/sql-server-hybrid-benefit/sql-always-on-architecture.png":::
 
+Microsoft SQL Server (2019 and 2022) was tested with Windows Server (2019 and 2022) Data Center edition with the virtual machines deployed in the on-premises environment. Windows Server and SQL Server have been configured following best practices and recommendations from Microsoft and VMware. The on-premises source infrastructure was VMware vSphere 7.0 Update 3 and VMware vSAN running on Dell PowerEdge servers and Intel Optane P4800X SSD NVMe devices.
+
 ## Prerequisites
 
 These are the prerequisites to migrating your SQL Server instance to Azure VMware Solution.
@@ -25,12 +27,17 @@ These are the prerequisites to migrating your SQL Server instance to Azure VMwar
 - VMware HCX must be configured between your on-premises datacenter and the Azure VMware Solution private cloud that runs the migrated workloads. For more information on how to configure HCX, see [Azure VMware Solution documentation](install-vmware-hcx.md).
 - Ensure that all the network segments in use by SQL Server and workloads using it are extended into your Azure VMware Solution private cloud. To verify this step, see [Configure VMware HCX network extension](configure-hcx-network-extension.md).
 
-VMware HCX over VPN is supported in Azure VMware Solution for workload migration.
-However, due to the size of database workloads, VMware HCX over VPN is not recommended for Microsoft SQL Server Always On FCI or AG migrations for production workloads.
-ExpressRoute connectivity is recommended as more performant and reliable. 
-For Microsoft SQL Server standalone and non-production workloads this may be suitable, depending upon the size of the database, to migrate. 
+Either VMware HCX over VPN or ExpressRoute connectivity can be used as the networking configuration for the migration.
 
-Microsoft SQL Server (2019 and 2022) was tested with Windows Server (2019 and 2022) Data Center edition with the virtual machines deployed in the on-premises environment. Windows Server and SQL Server have been configured following best practices and recommendations from Microsoft and VMware. The on-premises source infrastructure was VMware vSphere 7.0 Update 3 and VMware vSAN running on Dell PowerEdge servers and Intel Optane P4800X SSD NVMe devices.
+With VMWare HCX over VPN, due to its limited bandwidth it is typically suited for workloads that can sustain longer periods of downtime (such as non-production environments).
+
+For any of the following, ExpressRoute connectivity is recommended for a migration:
+
+- Production environments
+- Workloads with large database sizes
+- Scenarios in which there is a need to minimize downtime the ExpressRoute connectivity is recommended for the migration.
+
+Further downtime considerations are discussed in the next section.
 
 ## Downtime considerations
 

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

@@ -24,6 +24,10 @@ However, you can overcome this limitation by performing the steps shown in this
 > [!NOTE]
 > This procedure requires a full shutdown of the cluster. Since the SQL Server service will be unavailable during the migration, plan accordingly for the downtime period.  
 
+Microsoft SQL Server 2019 and 2022 were tested with Windows Server 2019 and 2022 Data Center edition with the virtual machines deployed in the on-premises environment. 
+Windows Server and SQL Server have been configured following best practices and recommendations from Microsoft and VMware. 
+The on-premises source infrastructure was VMware vSphere 7.0 Update 3 and VMware vSAN running on Dell PowerEdge servers and Intel Optane P4800X SSD NVMe devices.
+
 ## Prerequisites
 
 - Review and record the storage and network configuration of every node in the cluster.
@@ -34,14 +38,15 @@ However, you can overcome this limitation by performing the steps shown in this
 - VMware HCX must be configured between your on-premises datacenter and the Azure VMware Solution private cloud that runs the migrated workloads. For more details about installing VMware HCX, see [Azure VMware Solution documentation](install-vmware-hcx.md).
 - Ensure that all the network segments in use by SQL Server and workloads using it are extended into your Azure VMware Solution private cloud. To verify this step, see [Configure VMware HCX network extension](configure-hcx-network-extension.md).
 
-VMware HCX over VPN is supported in Azure VMware Solution for workload migration.
-However, due to the size of database workloads it isn't recommended for Microsoft SQL Server Failover Cluster Instance and Microsoft SQL Server Always On migrations, especially for production workloads.
-ExpressRoute connectivity is recommended as more performant and reliable.
-For Microsoft SQL Server Standalone and non-production workloads this can be suitable, depending upon the size of the database, to migrate.
+Either VMware HCX over VPN or ExpressRoute connectivity can be used as the networking configuration for the migration.
 
-Microsoft SQL Server 2019 and 2022 were tested with Windows Server 2019 and 2022 Data Center edition with the virtual machines deployed in the on-premises environment. 
-Windows Server and SQL Server have been configured following best practices and recommendations from Microsoft and VMware. 
-The on-premises source infrastructure was VMware vSphere 7.0 Update 3 and VMware vSAN running on Dell PowerEdge servers and Intel Optane P4800X SSD NVMe devices.
+With VMWare HCX over VPN, due to its limited bandwidth it is typically suited for workloads that can sustain longer periods of downtime (such as non-production environments).
+
+For any of the following, ExpressRoute connectivity is recommended for a migration:
+
+- Production environments
+- Workloads with large database sizes
+- Scenarios in which there is a need to minimize downtime the ExpressRoute connectivity is recommended for the migration.
 
 ## Downtime considerations
 

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

@@ -22,6 +22,13 @@ In both cases, consider the size and criticality of the database being migrated.
 For this how-to procedure, we have validated VMware HCX vMotion.
 VMware HCX Cold Migration is also valid, but it requires a longer downtime period.
 
+This scenario was validated using the following editions and configurations:
+
+- Microsoft SQL Server (2019 and 2022)  
+- Windows Server (2019 and 2022) Data Center edition  
+- Windows Server and SQL Server were configured following best practices and recommendations from Microsoft and VMware.  
+- The on-premises source infrastructure was VMware vSphere 7.0 Update 3 and VMware vSAN running on Dell PowerEdge servers and Intel Optane P4800X SSD NVMe devices.
+
 :::image type="content" source="media/sql-server-hybrid-benefit/migrated-sql-standalone-cluster.png" alt-text="Diagram showing the architecture of Standalone SQL Server for  Azure VMware Solution." border="false" lightbox="media/sql-server-hybrid-benefit/migrated-sql-standalone-cluster.png"::: 
 
 ## Prerequisites
@@ -34,21 +41,17 @@ VMware HCX Cold Migration is also valid, but it requires a longer downtime perio
 - 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).
 - 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).
 
-Either VMware HCX over VPN or ExpressRoute connectivity can be used as the networking configuration for the migration. 
+Either VMware HCX over VPN or ExpressRoute connectivity can be used as the networking configuration for the migration.
 
 With VMWare HCX over VPN, due to its limited bandwidth it is typically suited for workloads that can sustain longer periods of downtime (such as non-production environments).
 
-For production environments, or workloads with large database sizes or where there is a need to minimize downtime the ExpressRoute connectivity is recommended for the migration.  
-
-Further downtime considerations are discussed in the next section.
-
-This scenario was validated using the following editions and configurations:
+For any of the following, ExpressRoute connectivity is recommended for a migration:
 
-- Microsoft SQL Server (2019 and 2022)  
-- Windows Server (2019 and 2022) Data Center edition  
-- Windows Server and SQL Server were configured following best practices and recommendations from Microsoft and VMware.  
-- The on-premises source infrastructure was VMware vSphere 7.0 Update 3 and VMware vSAN running on Dell PowerEdge servers and Intel Optane P4800X SSD NVMe devices.
+- Production environments
+- Workloads with large database sizes
+- Scenarios in which there is a need to minimize downtime the ExpressRoute connectivity is recommended for the migration.migration.  
 
+Further downtime considerations are discussed in the next section.
 
 ## Downtime considerations