Merge pull request #233936 from roygara/pv2Sector

Adding premv2 sector size

Author: v-regandowner

articles/virtual-machines/disks-deploy-premium-v2.md

@@ -3,7 +3,7 @@ title: Deploy a Premium SSD v2 managed disk
 description: Learn how to deploy a Premium SSD v2.
 author: roygara
 ms.author: rogarana
-ms.date: 03/16/2023
+ms.date: 04/10/2023
 ms.topic: how-to
 ms.service: storage
 ms.subservice: disks
@@ -14,6 +14,8 @@ ms.custom: references_regions, ignite-2022, devx-track-azurecli, devx-track-azur
 
 Azure Premium SSD v2 is designed for IO-intense enterprise workloads that require sub-millisecond disk latencies and high IOPS and throughput at a low cost. Premium SSD v2 is suited for a broad range of workloads such as SQL server, Oracle, MariaDB, SAP, Cassandra, Mongo DB, big data/analytics, gaming, on virtual machines or stateful containers. For conceptual information on Premium SSD v2, see [Premium SSD v2](disks-types.md#premium-ssd-v2).
 
+Premium SSD v2 support a 4k physical sector size by default, but can be configured to use a 512E sector size as well. While most applications are compatible with 4k sector sizes, some require 512 byte sector sizes. Oracle Database, for example, requires release 12.2 or later in order to support 4k native disks. For older versions of Oracle DB, 512 byte sector size is required.
+
 ## Limitations
 
 [!INCLUDE [disks-prem-v2-limitations](../../includes/disks-prem-v2-limitations.md)]
@@ -66,14 +68,15 @@ Now that you know the region and zone to deploy to, follow the deployment steps
 
 # [Azure CLI](#tab/azure-cli)
 
-Create a Premium SSD v2 disk in an availability zone. Then create a VM in the same region and availability zone that supports Premium Storage and attach the disk to it. Replace the values of all the variables with your own, then run the following script:
+Create a Premium SSD v2 disk in an availability zone. Then create a VM in the same region and availability zone that supports Premium Storage and attach the disk to it. The following script creates a Premium SSD v2 with a 4k sector size, to deploy one with a 512 sector size, update the `$logicalSectorSize` parameter. Replace the values of all the variables with your own, then run the following script:
 
 ```azurecli-interactive
 ## Initialize variables
 diskName="yourDiskName"
 resourceGroupName="yourResourceGroupName"
 region="yourRegionName"
 zone="yourZoneNumber"
+##Replace 4096 with 512 to deploy a disk with 512 sector size
 logicalSectorSize=4096
 vmName="yourVMName"
 vmImage="Win2016Datacenter"
@@ -103,7 +106,7 @@ az vm create -n $vmName -g $resourceGroupName \
 
 # [PowerShell](#tab/azure-powershell)
 
-Create a Premium SSD v2 disk in an availability zone. Then create a VM in the same region and availability zone that supports Premium Storage and attach the disk to it. Replace the values of all the variables with your own, then run the following script:
+Create a Premium SSD v2 disk in an availability zone. Then create a VM in the same region and availability zone that supports Premium Storage and attach the disk to it. The following script creates a Premium SSD v2 with a 4k sector size, to deploy one with a 512 sector size, update the `$logicalSectorSize` parameter. Replace the values of all the variables with your own, then run the following script:
 
 ```powershell
 # Initialize variables
@@ -114,6 +117,7 @@ $diskName = "yourDiskName"
 $diskSizeInGiB = 100
 $diskIOPS = 5000
 $diskThroughputInMBPS = 150
+#To use a 512 sector size, replace 4096 with 512
 $logicalSectorSize=4096
 $lun = 1
 $vmName = "yourVMName"
@@ -175,6 +179,10 @@ Update-AzVM -VM $vm -ResourceGroupName $resourceGroupName
 
     :::image type="content" source="media/disks-deploy-premium-v2/premv2-select.png" alt-text="Screenshot selecting Premium SSD v2 SKU." lightbox="media/disks-deploy-premium-v2/premv2-select.png":::
 
+1. Select whether you'd like to deploy a 4k or 512 logical sector size.
+
+    :::image type="content" source="media/disks-deploy-premium-v2/premv2-sector-size.png" alt-text="Screenshot of deployment logical sector size deployment options." lightbox="media/disks-deploy-premium-v2/premv2-sector-size.png":::
+
 1. Proceed through the rest of the VM deployment, making any choices that you desire.
 
 You've now deployed a VM with a premium SSD v2.

articles/virtual-machines/disks-types.md

@@ -3,7 +3,7 @@ title: Select a disk type for Azure IaaS VMs - managed disks
 description: Learn about the available Azure disk types for virtual machines, including ultra disks, Premium SSDs v2, Premium SSDs, standard SSDs, and Standard HDDs.
 author: roygara
 ms.author: rogarana
-ms.date: 03/16/2023
+ms.date: 04/10/2023
 ms.topic: conceptual
 ms.service: storage
 ms.subservice: disks
@@ -97,6 +97,8 @@ If you would like to start using ultra disks, see the article on [using Azure ul
 
 Azure Premium SSD v2 is designed for IO-intense enterprise workloads that require consistent sub-millisecond disk latencies and high IOPS and throughput at a low cost. The performance (capacity, throughput, and IOPS) of Premium SSD v2 disks can be independently configured at any time, making it easier for more scenarios to be cost efficient while meeting performance needs. For example, a transaction-intensive database workload may need a large amount of IOPS at a small size, or a gaming application may need a large amount of IOPS during peak hours. Premium SSD v2 is suited for a broad range of workloads such as SQL server, Oracle, MariaDB, SAP, Cassandra, Mongo DB, big data/analytics, and gaming, on virtual machines or stateful containers.
 
+Premium SSD v2 support a 4k physical sector size by default, but can be configured to use a 512E sector size as well. While most applications are compatible with 4k sector sizes, some require 512 byte sector sizes. Oracle Database, for example, requires release 12.2 or later in order to support 4k native disks. For older versions of Oracle DB, 512 byte sector size is required.
+
 ### Differences between Premium SSD and Premium SSD v2
 
 Unlike Premium SSDs, Premium SSD v2 doesn't have dedicated sizes. You can set a Premium SSD v2 to any supported size you prefer, and make granular adjustments to the performance without downtime. Premium SSD v2 doesn't support host caching but, benefits significantly from lower latency which addresses some of the same core problems host caching addresses. The ability to adjust IOPS, throughput, and size at any time also means you can avoid the maintenance overhead of having to stripe disks to meet your needs.