Merge pull request #29614 from MashaMSFT/202401_sqlvmstv2

Staging preview of Premium SSD v2

Author: denrea

.openpublishing.publish.config.json

@@ -134,6 +134,12 @@
       "branch": "master",
       "branch_mapping": {}
     },
+    {
+      "path_to_root": "azure-docs-pr",
+      "url": "https://github.com/MicrosoftDocs/azure-docs-pr",
+      "branch": "master",
+      "branch_mapping": {}
+    },
     {
       "path_to_root": "azure-sql/reusable-content",
       "url": "https://github.com/MicrosoftDocs/reusable-content",

azure-sql/includes/sql-vm-feature-benefits.md

@@ -15,7 +15,7 @@ ms.topic: include
 | **Azure Update Manager integration** | Since Automated Patching doesn't install Cumulative Updates for SQL Server, you can replace it with by integrating [Azure Update Manager](../virtual-machines/azure-update-manager-sql-vm.md) into your SQL virtual machines resource, which adds improved patching functionality for your SQL Server VMs.  This feature is currently in preview. | 
 | **Flexible licensing** | Save on cost by [seamlessly transitioning](../virtual-machines/windows/licensing-model-azure-hybrid-benefit-ahb-change.md) from the bring-your-own-license (also known as the Azure Hybrid Benefit) to the pay-as-you-go licensing model and back again. <br /> <br /> Included with basic registration. | 
 | **Flexible version / edition** | If you decide to change the [version](../virtual-machines/windows/change-sql-server-version.md) or [edition](../virtual-machines/windows/change-sql-server-edition.md) of SQL Server, you can update the metadata within the Azure portal without having to redeploy the entire SQL Server VM.  <br /> <br /> Included with basic registration.   | 
-| **Configure tempdb** | You can [configure your tempdb](../virtual-machines/windows/manage-sql-vm-portal.md#storage) directly from the Azure portal, such as specifying the number of files, their initial size, their location, and the autogrowth ratio. Restart your SQL Server service for the changes to take effect. <br /> <br /> Requires SQL IaaS Agent extension.  | 
+| **Configure tempdb** | You can [configure your tempdb](../virtual-machines/windows/manage-sql-vm-portal.md#storage-configuration) directly from the Azure portal, such as specifying the number of files, their initial size, their location, and the autogrowth ratio. Restart your SQL Server service for the changes to take effect. <br /> <br /> Requires SQL IaaS Agent extension.  | 
 | **Defender for Cloud portal integration** | If you've enabled [Microsoft Defender for SQL](/azure/defender-for-cloud/defender-for-sql-usage), then you can view Defender for Cloud recommendations directly in the [SQL virtual machines](../virtual-machines/windows/manage-sql-vm-portal.md) resource of the Azure portal. See [Security best practices](../virtual-machines/windows/security-considerations-best-practices.md) to learn more. <br /> <br /> Requires SQL IaaS Agent extension. |
 | **SQL best practices assessment** | Enables you to assess the health of your SQL Server VMs using configuration best practices. For more information, see [SQL best practices assessment](../virtual-machines/windows/sql-assessment-for-sql-vm.md). <br /> <br /> Requires SQL IaaS Agent extension. | 
 | **View disk utilization in portal** | Allows you to view a graphical representation of the disk utilization of your SQL data files in the Azure portal. <br /> <br /> Requires SQL IaaS Agent extension. | 

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

@@ -1,22 +1,23 @@
 ---
 author: MashaMSFT
 ms.author: mathoma
-ms.date: 10/22/2023
+ms.date: 03/01/2024
 ms.service: virtual-machines
 ms.topic: include
 ---
 - Monitor the application and [determine storage bandwidth and latency requirements](/azure/virtual-machines/premium-storage-performance#counters-to-measure-application-performance-requirements) for SQL Server data, log, and `tempdb` files before choosing the disk type.
-- If available, configure the `tempdb` [data and log files on the D: local SSD volume](../virtual-machines/windows/manage-sql-vm-portal.md#storage). The SQL IaaS Agent extension handles the folder and permissions needed upon re-provisioning.
+- If available, configure the `tempdb` [data and log files on the D: local SSD volume](../virtual-machines/windows/storage-configuration.md#new-vms). The SQL IaaS Agent extension handles the folder and permissions needed upon re-provisioning.
 - To optimize storage performance, plan for highest uncached IOPS available and use data caching as a performance feature for data reads while avoiding [virtual machine and disks capping](/azure/virtual-machines/premium-storage-performance#throttling).
+- When using the [Ebdsv5 or Ebsv5](/azure/virtual-machines/ebdsv5-ebsv5-series) series SQL Server VMs, use [Premium SSD v2](../virtual-machines/windows/storage-configuration-premium-ssd-v2.md) for the best price performance. You can deploy your SQL Server VM with Premium SSD v2 by using the Azure portal (currently in preview). 
 - Consider using [Azure Elastic SAN](../virtual-machines/windows/performance-guidelines-best-practices-storage.md#azure-elastic-san) for SQL Server workloads for better cost-efficiency due to storage consolidation, shared dynamic performance and the ability to drive higher storage throughput without needing to upgrade a VM. 
-- 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](/azure/virtual-machines/disks-types#premium-ssd-v2) which provides better price-performance for workloads that require high IOPS and I/O throughput.
+- 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](/azure/virtual-machines/disks-types#premium-ssd-v2) or [Azure ultra disks](/azure/virtual-machines/disks-types#ultra-disks) for the transaction log.
+    - 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 (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 FCI place `tempdb` on the shared storage.
+  - For failover cluster instances (FCI) place `tempdb` on the shared storage.
     - If the FCI workload is heavily dependent on `tempdb` disk performance, then as an advanced configuration place `tempdb` on the local ephemeral SSD (default `D:\`) drive, which isn't part of FCI storage. This configuration needs custom monitoring and action to ensure the local ephemeral SSD (default `D:\`) drive is available all the time as any failures of this drive won't trigger action from FCI.
 - Stripe multiple Azure data disks using [Storage Spaces](/windows-server/storage/storage-spaces/overview) to increase I/O bandwidth up to the target virtual machine's IOPS and throughput limits.
 - Set [host caching](/azure/virtual-machines/disks-performance#virtual-machine-uncached-vs-cached-limits) to **read-only** for data file disks.
@@ -32,4 +33,3 @@ ms.topic: include
 - Enable the [SQL Best Practices Assessment](../virtual-machines/windows/sql-assessment-for-sql-vm.md) to identify possible performance issues and evaluate that your SQL Server VM is configured to follow best practices.
 - Review and monitor disk and VM limits using [Storage IO utilization metrics](/azure/virtual-machines/disks-metrics#storage-io-utilization-metrics).
 - [Exclude SQL Server files](/troubleshoot/sql/database-engine/security/antivirus-and-sql-server) from antivirus software scanning, including data files, log files, and backup files.
-

azure-sql/toc.yml

@@ -1659,8 +1659,10 @@
           href: virtual-machines/windows/change-sql-server-edition.md
         - name: Change version
           href: virtual-machines/windows/change-sql-server-version.md
-        - name: Storage
+        - name: Storage configuration
           href: virtual-machines/windows/storage-configuration.md
+        - name: Premium SSD v2 (preview)
+          href: virtual-machines/windows/storage-configuration-premium-ssd-v2.md
         - name: Microsoft Entra authentication
           href: virtual-machines/windows/configure-azure-ad-authentication-for-sql-vm.md
         - name: Azure Update Manager
@@ -1671,7 +1673,7 @@
           href: virtual-machines/windows/sql-assessment-for-sql-vm.md
         - name: Azure Key Vault Integration
           href: virtual-machines/windows/azure-key-vault-integration-configure.md
-        - name: Migrate storage to UltraSSD
+        - name: Migrate storage to Ultradisk
           href: virtual-machines/windows/storage-migrate-to-ultradisk.md
         - name: SQL IaaS Agent extension
           displayName: resource provider, registration, sql vm rp

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

@@ -4,7 +4,7 @@ description: Learn about the features and documentation improvements for SQL Ser
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: wiassaf
-ms.date: 12/19/2023
+ms.date: 03/01/2024
 ms.service: virtual-machines-sql
 ms.subservice: service-overview
 ms.topic: whats-new
@@ -31,23 +31,24 @@ Return to [What's new in SQL Server on Azure VMs?](doc-changes-updates-release-n
 | **Azure SQL bindings for Azure Functions GA** | May | Azure Functions supports input bindings, and output bindings for the Azure SQL and SQL Server products. This feature is now generally available. Review [Azure SQL bindings for Azure Functions](/azure/azure-functions/functions-bindings-azure-sql) to learn more.  | 
 | **Azure SQL triggers for Azure Functions preview**|  May |  Azure Functions supports function triggers for the Azure SQL and SQL Server products. This feature is currently in preview. Review [Azure SQL triggers for Azure Functions](/azure/azure-functions/functions-bindings-azure-sql-trigger) to learn more. | 
 | **Auto upgrade SQL IaaS Agent extension** | April | It's now possible to enable auto upgrade for your SQL IaaS Agent extension to ensure you're automatically receiving the latest updates to the extension every month. Review [SQL IaaS Agent Settings](manage-sql-vm-portal.md#sql-iaas-agent-extension-settings) to learn more. 
-| **Azure AD authentication GA** | April | Microsoft Entra authentication is now generally available. Review [Configure Microsoft Entra authentication](configure-azure-ad-authentication-for-sql-vm.md) to learn more. |  
+| **Microsoft Entra authentication GA** | April | Microsoft Entra authentication is now generally available. Review [Configure Microsoft Entra authentication](configure-azure-ad-authentication-for-sql-vm.md) to learn more. |  
 | **Migrate AG to multi-subnet** | April | Learn how to migrate your single-subnet Always On availability group to multiple subnets to remove the reliance on an Azure Load Balancer or Distributed Network Name (DNN) to route traffic to your listener. See [Migrate availability group to a multi-subnet environment](availability-group-manually-migrate-multi-subnet.md) to learn more. | 
 | **Removed extension management modes** | March | The architecture for the SQL IaaS Agent extension has been updated to remove management modes. All newly deployed SQL Server VMs are registered with the extension by using the same default configuration and least privileged security model. To learn more, review [Management modes](sql-server-iaas-agent-extension-automate-management.md#management-modes). |
-| **Enable Azure AD for SQL Server** |February | We've published a guide to help you enable Azure AD authentication for your SQL Server VM. Review [Configure Azure AD](configure-azure-ad-authentication-for-sql-vm.md) to learn more. | 
+| **Enable Microsoft Entra for SQL Server** |February | We've published a guide to help you enable Microsoft Entra authentication for your SQL Server VM. Review [Configure Microsoft Entra](configure-azure-ad-authentication-for-sql-vm.md) to learn more. | 
 | **Extend your multi-subnet AG to multiple regions** | January | Extend an existing multi-subnet availability group, either on Azure virtual machines, or on-premises, to another region in Azure. To learn more, review [Multi-subnet availability group in multiple regions](availability-group-manually-configure-multi-subnet-multiple-regions.md). | 
 
+
 ## 2022
 
 | Changes | Details |
 | --- | --- |
 | **Troubleshoot SQL IaaS Agent extension** | We've added an article to help you troubleshoot and address some known issues with the SQL Server IaaS agent extension. To learn more, read [Troubleshoot known issues](sql-agent-extension-troubleshoot-known-issues.md). |
 | **Configure AG from Azure portal** | There is a new experience to deploy an Always On availability group to multiple subnets by using the Azure portal. The new availability group deployment method replaces the previous deployment through the SQL virtual machines resource. This feature is currently in preview. To learn more, review [Configure availability group through the Azure portal](availability-group-azure-portal-configure.md). | 
-| **Azure AD authentication** | It's now possible to configure Azure Active Directory (Azure AD) authentication to your SQL Server 2022 on Azure VM by using the Azure portal. This feature is currently in preview. To get started, review [Azure AD with SQL Server VMs](security-considerations-best-practices.md#azure-ad-authentication). | 
+| **Microsoft Entra authentication** | It's now possible to configure Microsoft Entra authentication to your SQL Server 2022 on Azure VM by using the Azure portal. This feature is currently in preview. To get started, review [Microsoft Entra with SQL Server VMs](security-considerations-best-practices.md#azure-ad-authentication). | 
 | **Least privilege permission model for SQL IaaS Agent extension** | There is a new permissions model available for the SQL Server IaaS Agent extension that grants the least privileged permission for each feature used by the extension. To learn more, review [SQL IaaS Agent extension permissions](sql-server-iaas-agent-extension-automate-management.md#permissions-models). | 
 | **Confidential VMs** | SQL Server on Azure VMs has added support to deploy to [SQL Server on Azure confidential VMs](sql-vm-create-confidential-vm-how-to.md). To get started, review the [Quickstart: Deploy SQL Server to an Azure confidential VM](sql-vm-create-portal-quickstart.md?tabs=confidential-vm). 
 | **Azure CLI for SQL best practices assessment**| It's now possible to configure the [SQL best practices assessment](sql-assessment-for-sql-vm.md) feature using the Azure CLI. |
-| **Configure tempdb from Azure portal** | It's now possible to configure your `tempdb` settings, such as the number of files, initial size, and autogrowth ratio for an existing SQL Server instance by using the Azure portal. See [manage SQL Server VM from portal](manage-sql-vm-portal.md#storage) to learn more. |
+| **Configure tempdb from Azure portal** | It's now possible to configure your `tempdb` settings, such as the number of files, initial size, and autogrowth ratio for an existing SQL Server instance by using the Azure portal. See [manage SQL Server VM from portal](manage-sql-vm-portal.md#storage-configuration) to learn more. |
 | **SDK-style SQL projects**| Use [Microsoft.Build.Sql](https://www.nuget.org/packages/Microsoft.Build.Sql) for SDK-style SQL projects in the SQL Database Projects extension in Azure Data Studio or VS Code. This feature is currently in preview. To learn more, see [SDK-style SQL projects](/azure-data-studio/extensions/sql-database-project-extension-sdk-style-projects). |
 | **Ebdsv5-series** | The new [Ebdsv5-series](/azure/virtual-machines/ebdsv5-ebsv5-series#ebdsv5-series) provides the highest I/O throughput-to-vCore ratio in Azure along with a memory-to-vCore ratio of 8. This series offers the best price-performance for SQL Server workloads on Azure VMs. Consider this series first for most SQL Server workloads. To learn more, see the updates in [VM sizes](performance-guidelines-best-practices-vm-size.md). |
 | **Security best practices** | The [SQL Server VM security best practices](security-considerations-best-practices.md) have been rewritten and refreshed! |