Initial plan (#36724)

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: eh8 <22990581+eh8@users.noreply.github.com>

Author: eh8

azure-sql/includes/virtual-machines-best-practices-storage.md

@@ -17,8 +17,8 @@ ms.topic: include
 - Place data, log, and `tempdb` files on separate drives.  
   - For the data drive, use [premium P30 and P40 or smaller disks](/azure/virtual-machines/disks-types#premium-ssds) to ensure the availability of cache support. When using the [Ebdsv5 VM series](/azure/virtual-machines/ebdsv5-ebsv5-series), use [Premium SSD v2](../virtual-machines/windows/storage-configuration-premium-ssd-v2.md) which provides better price-performance for workloads that require high IOPS and I/O throughput.
   - For the log drive plan for capacity and test performance versus cost while evaluating either [Premium SSD v2](/azure/virtual-machines/disks-types#premium-ssd-v2) or Premium SSD [P30 - P80 disks](/azure/virtual-machines/disks-types#premium-ssds)
-    - If submillisecond storage latency is required, use either [Premium SSD v2](../virtual-machines/windows/storage-configuration-premium-ssd-v2.md) or [Azure ultra disks](/azure/virtual-machines/disks-types#ultra-disks) for the transaction log.
-    - For M-series virtual machine deployments, consider [write accelerator](/azure/virtual-machines/how-to-enable-write-accelerator) over using Azure ultra disks.
+    - If submillisecond storage latency is required, use either [Premium SSD v2](../virtual-machines/windows/storage-configuration-premium-ssd-v2.md) or [Azure Ultra Disks](/azure/virtual-machines/disks-types#ultra-disks) for the transaction log.
+    - For M-series virtual machine deployments, consider [write accelerator](/azure/virtual-machines/how-to-enable-write-accelerator) over using Azure Ultra Disks.
   - Place [tempdb](/sql/relational-databases/databases/tempdb-database) on the [temporary disk](../virtual-machines/windows/tempdb-ephemeral-storage.md) (the temporary disk is ephemeral, and defaults to `D:\`) for most SQL Server workloads that aren't part of a failover cluster instance (FCI) after choosing the optimal VM size.
     - If the capacity of the local drive isn't enough for `tempdb`, consider sizing up the VM. For more information, see [Data file caching policies](../virtual-machines/windows/performance-guidelines-best-practices-storage.md#data-file-caching-policies).
   - For failover cluster instances (FCI) place `tempdb` on the shared storage.

azure-sql/toc.yml

@@ -1657,7 +1657,7 @@
         items:
         - name: VM to a new region
           href: virtual-machines/windows/move-sql-vm-different-region.md
-        - name: Migrate storage to Ultradisk
+        - name: Migrate storage to Ultra Disk
           href: virtual-machines/windows/storage-migrate-to-ultradisk.md
       - name: Business continuity
         items:

azure-sql/virtual-machines/modernization-advisor.md

@@ -38,7 +38,7 @@ Modernization Advisor evaluates the following SQL Server VM resources to match w
 - The number of vCores
 - Memory used per vCore
 - Storage size
-- Storage type (Standard, Premium SSD, Premium SSDv2)
+- Storage type (Standard, Premium SSD, Premium SSD v2)
 
 ## Potential migration benefits 
 

azure-sql/virtual-machines/windows/availability-group-manually-configure-multiple-regions.md

@@ -230,11 +230,11 @@ After the domain controller restarts, the next step is to [Create a SQL Server v
 
 Before you proceed, consider the following design decisions:
 
-- **Storage: Azure managed disks**
+- **Storage: Azure Managed Disks**
 
-  For the virtual machine storage, use Azure managed disks. We recommend managed disks for SQL Server virtual machines. Managed disks handle storage behind the scenes. In addition, when virtual machines with managed disks are in the same availability set, Azure distributes the storage resources to provide appropriate redundancy.
+  For the virtual machine storage, use Azure Managed Disks. We recommend managed disks for SQL Server virtual machines. Managed disks handle storage behind the scenes. In addition, when virtual machines with managed disks are in the same availability set, Azure distributes the storage resources to provide appropriate redundancy.
 
-  For more information, see [Introduction to Azure managed disks](/azure/virtual-machines/managed-disks-overview). For specifics about managed disks in an availability set, see [Use managed disks for VMs in an availability set](/azure/virtual-machines/availability).
+  For more information, see [Introduction to Azure Managed Disks](/azure/virtual-machines/managed-disks-overview). For specifics about managed disks in an availability set, see [Use managed disks for VMs in an availability set](/azure/virtual-machines/availability).
 
 - **Network: Private IP addresses in production**
 

azure-sql/virtual-machines/windows/availability-group-manually-configure-prerequisites-tutorial-single-subnet.md

@@ -357,11 +357,11 @@ Windows Server 2016 and later versions can use a [cloud witness](/windows-server
 
 Before you proceed, consider the following design decisions:
 
-- **Storage: Azure managed disks**
+- **Storage: Azure Managed Disks**
 
-  For the virtual machine storage, use Azure managed disks. We recommend managed disks for SQL Server virtual machines. Managed disks handle storage behind the scenes. In addition, when virtual machines with managed disks are in the same availability set, Azure distributes the storage resources to provide appropriate redundancy.
+  For the virtual machine storage, use Azure Managed Disks. We recommend managed disks for SQL Server virtual machines. Managed disks handle storage behind the scenes. In addition, when virtual machines with managed disks are in the same availability set, Azure distributes the storage resources to provide appropriate redundancy.
 
-  For more information, see [Introduction to Azure managed disks](/azure/virtual-machines/managed-disks-overview). For specifics about managed disks in an availability set, see [Availability options for Azure virtual machines](/azure/virtual-machines/availability).
+  For more information, see [Introduction to Azure Managed Disks](/azure/virtual-machines/managed-disks-overview). For specifics about managed disks in an availability set, see [Availability options for Azure virtual machines](/azure/virtual-machines/availability).
 
 - **Network: Private IP addresses in production**
 

azure-sql/virtual-machines/windows/create-sql-vm-powershell.md

@@ -46,7 +46,7 @@ Modify as you want and then run these cmdlets to initialize these variables.
 
 Define the storage account and the type of storage to be used by the virtual machine.
 
-Modify as you want, and then run the following cmdlet to initialize these variables. We recommend using [premium SSDs](/azure/virtual-machines/disks-types#premium-ssds) for production workloads.
+Modify as you want, and then run the following cmdlet to initialize these variables. We recommend using [Premium SSDs](/azure/virtual-machines/disks-types#premium-ssds) for production workloads.
 
 :::code language="powershell" source="~/../azure_powershell_scripts/azure-sql/virtual-machine/create-sql-server-vm.ps1" id="StorageVariables":::
 

azure-sql/virtual-machines/windows/doc-changes-updates-release-notes-whats-new-archive.md

@@ -118,7 +118,7 @@ Return to [What's new in SQL Server on Azure VMs?](doc-changes-updates-release-n
 | **Distributed network name (DNN)** | SQL Server 2019 on Windows Server 2016+ is now previewing support for routing traffic to your failover cluster instance (FCI) by using a [distributed network name](./failover-cluster-instance-distributed-network-name-dnn-configure.md) rather than using Azure Load Balancer. This support simplifies and streamlines connecting to your high-availability (HA) solution in Azure. | 
 | **FCI with Azure shared disks** | It's now possible to deploy your [failover cluster instance (FCI)](failover-cluster-instance-overview.md) by using [Azure shared disks](failover-cluster-instance-azure-shared-disks-manually-configure.md). |
 | **Reorganized FCI docs** | The documentation around [failover cluster instances with SQL Server on Azure VMs](failover-cluster-instance-overview.md) has been rewritten and reorganized for clarity. We've separated some of the configuration content, like the [cluster configuration best practices](hadr-cluster-best-practices.md), how to prepare a [virtual machine for a SQL Server FCI](failover-cluster-instance-prepare-vm.md), and how to configure [Azure Load Balancer](./availability-group-vnn-azure-load-balancer-configure.md). | 
-| **Migrate log to ultra disk** | Learn how you can [migrate your log file to an ultra disk](storage-migrate-to-ultradisk.md) to leverage high performance and low latency. | 
+| **Migrate log to Ultra Disk** | Learn how you can [migrate your log file to an Ultra Disk](storage-migrate-to-ultradisk.md) to leverage high performance and low latency. | 
 | **Create availability group using Azure PowerShell** | It's now possible to simplify the creation of an availability group by using [Azure PowerShell](availability-group-az-commandline-configure.md) as well as the Azure CLI. | 
 | **Configure availability group in portal** | It's now possible to [configure your availability group via the Azure portal](availability-group-azure-portal-configure.md). This feature is currently in preview and being deployed so if your desired region is unavailable, check back soon. | 
 | **Automatic extension registration** | You can now enable the [Automatic registration](sql-agent-extension-automatic-registration-all-vms.md) feature to automatically register all SQL Server VMs already deployed to your subscription with the [SQL IaaS Agent extension](sql-server-iaas-agent-extension-automate-management.md). This applies to all existing VMs, and will also automatically register all SQL Server VMs added in the future.   | 

azure-sql/virtual-machines/windows/failover-cluster-instance-azure-shared-disks-manually-configure.md

@@ -40,7 +40,7 @@ Before you complete the instructions in this article, you should already have:
 ## Add Azure shared disk
 
 [Deploy a managed disk with the shared disk feature enabled](/azure/virtual-machines/disks-shared-enable#deploy-shared-disks). Set `maxShares` to **align with the number of cluster nodes** to make the disk shareable across all FCI nodes.
-Premium SSD, Premium SSDv2 and Ultra Disk are supported disk types to use with a SQL Server failover cluster instance. 
+Premium SSD, Premium SSD v2 and Ultra Disk are supported disk types to use with a SQL Server failover cluster instance. 
 
 Use zone-redundant storage (ZRS) whenever possible. 
 

azure-sql/virtual-machines/windows/failover-cluster-instance-overview.md

@@ -48,15 +48,15 @@ SQL Server on Azure VMs offers various options as a shared storage solution for
 | --- | --- | --- | --- | --- |
 | **Minimum OS version** | All | Windows Server 2012 | Windows Server 2016 | Windows Server 2022 |
 | **Minimum SQL Server version** | All | SQL Server 2012 | SQL Server 2016 |SQL Server 2022 |
-| **Supported VM availability** | [Premium SSD LRS](/azure/virtual-machines/disks-redundancy#locally-redundant-storage-for-managed-disks): Availability Sets with or without [proximity placement group](/azure/virtual-machines/windows/proximity-placement-groups-portal)<br />[Premium SSD ZRS](/azure/virtual-machines/disks-redundancy#zone-redundant-storage-for-managed-disks): Availability zones<br />[Ultra disks](/azure/virtual-machines/disks-enable-ultra-ssd): Same availability zone | Availability sets and availability zones | Availability sets | Availability zones |
+| **Supported VM availability** | [Premium SSD LRS](/azure/virtual-machines/disks-redundancy#locally-redundant-storage-for-managed-disks): Availability Sets with or without [proximity placement group](/azure/virtual-machines/windows/proximity-placement-groups-portal)<br />[Premium SSD ZRS](/azure/virtual-machines/disks-redundancy#zone-redundant-storage-for-managed-disks): Availability zones<br />[Ultra Disks](/azure/virtual-machines/disks-enable-ultra-ssd): Same availability zone | Availability sets and availability zones | Availability sets | Availability zones |
 | **Supports FileStream** | Yes | No | Yes | No |
 | **Supports MSDTC** | Yes | No | No | No |
 
 The rest of this section lists the benefits and limitations of each storage option available for SQL Server on Azure VMs.
 
 ### Azure shared disks
 
-[Azure shared disks](/azure/virtual-machines/disks-shared) are a feature of [Azure managed disks](/azure/virtual-machines/managed-disks-overview). Windows Server Failover Clustering supports using Azure shared disks with a failover cluster instance.
+[Azure shared disks](/azure/virtual-machines/disks-shared) are a feature of [Azure Managed Disks](/azure/virtual-machines/managed-disks-overview). Windows Server Failover Clustering supports using Azure shared disks with a failover cluster instance.
 
 **Supported OS**: All   
 **Supported SQL version**: All
@@ -65,7 +65,7 @@ The rest of this section lists the benefits and limitations of each storage opti
 
 - Useful for applications looking to migrate to Azure while keeping their high-availability and disaster recovery (HADR) architecture as is.
 - Can migrate clustered applications to Azure as is because of SCSI Persistent Reservations (SCSI PR) support.
-- Supports shared Azure Premium SSD, Premium SSDv2, and Azure Ultra Disk storage.
+- Supports shared Azure Premium SSD, Premium SSD v2, and Azure Ultra Disk storage.
 - Can use a single shared disk or stripe multiple shared disks to create a shared storage pool.
 - Supports FILESTREAM.
 - Premium SSDs support availability sets.
@@ -77,8 +77,8 @@ The rest of this section lists the benefits and limitations of each storage opti
 
 **Limitations**:
 
-- Premium SSD disk caching isn't supported.
-- Ultra disks don't support availability sets or Zone Redundant Storage (ZRS).
+- Premium SSD caching isn't supported.
+- Ultra Disks don't support availability sets or Zone Redundant Storage (ZRS).
 - Availability zones are supported for Ultra Disks, but the VMs must be in the same availability zone, which reduces the availability of the virtual machine to 99.9%.
 
 To get started, see [Configure failover cluster instance with Azure shared disks](failover-cluster-instance-azure-shared-disks-manually-configure.md).

azure-sql/virtual-machines/windows/failover-cluster-instance-prepare-vm.md

@@ -46,16 +46,16 @@ The failover cluster feature requires virtual machines to be placed in an [avail
 
 Carefully select the VM availability option that matches your intended cluster configuration:
 
-- **Azure shared disks**: the availability option varies if you're using Premium SSD or UltraDisk:
+- **Azure shared disks**: the availability option varies if you're using Premium SSD or Ultra Disk:
 
   - **Premium SSD Zone Redundant Storage (ZRS)**:
-    [Availability Zone](/azure/reliability/availability-zones-overview) in different zones. [Premium SSD ZRS](/azure/virtual-machines/disks-redundancy#zone-redundant-storage-for-managed-disks) replicates your Azure managed disk synchronously across three Azure availability zones in the selected region. VMs part of failover cluster can be placed in different availability zones, helping you achieve a zone-redundant SQL Server FCI that provides a VM availability SLA of 99.99%. Disk latency for ZRS is higher due to the cross-zonal copy of data.
+    [Availability Zone](/azure/reliability/availability-zones-overview) in different zones. [Premium SSD ZRS](/azure/virtual-machines/disks-redundancy#zone-redundant-storage-for-managed-disks) replicates your Azure Managed Disk synchronously across three Azure availability zones in the selected region. VMs part of failover cluster can be placed in different availability zones, helping you achieve a zone-redundant SQL Server FCI that provides a VM availability SLA of 99.99%. Disk latency for ZRS is higher due to the cross-zonal copy of data.
 
   - **Premium SSD Locally Redundant Storage (LRS)**:
     [Availability Set](/azure/virtual-machines/windows/tutorial-availability-sets#create-an-availability-set) in different fault/update domains for [Premium SSD LRS](/azure/virtual-machines/disks-redundancy#locally-redundant-storage-for-managed-disks). You can also choose to place the VMs inside a [proximity placement group](/azure/virtual-machines/windows/proximity-placement-groups-portal) to locate them closer to each other. Combining availability set and proximity placement group provides the lowest latency for shared disks as data is replicated locally within one data center and provides VM availability SLA of 99.95%.
 
   - **Ultra Disk Locally Redundant Storage (LRS)**:
-    [Availability zones](/azure/virtual-machines/windows/create-portal-availability-zone#confirm-zone-for-managed-disk-and-ip-address) but the VMs must be placed in the same availability zone. [Ultra disks](/azure/virtual-machines/disks-enable-ultra-ssd) offers lowest disk latency and is best for IO intensive workloads. Since all VMs that are part of the FCI have to be in the same availability zone, the VM availability is only 99.9%.
+    [Availability zones](/azure/virtual-machines/windows/create-portal-availability-zone#confirm-zone-for-managed-disk-and-ip-address) but the VMs must be placed in the same availability zone. [Ultra Disks](/azure/virtual-machines/disks-enable-ultra-ssd) offers lowest disk latency and is best for IO intensive workloads. Since all VMs that are part of the FCI have to be in the same availability zone, the VM availability is only 99.9%.
 
 - **Premium file shares**: [Availability set](/azure/virtual-machines/windows/tutorial-availability-sets#create-an-availability-set) or [availability zones](/azure/virtual-machines/windows/create-portal-availability-zone#confirm-zone-for-managed-disk-and-ip-address).
 - **Storage Spaces Direct**: [Availability Set](/azure/virtual-machines/windows/tutorial-availability-sets#create-an-availability-set).