Merge pull request #242588 from msjuergent/pv2

based on new tests document that sector size does not matter

Author: prmerger-automator[bot]

articles/sap/workloads/hana-vm-premium-ssd-v2.md

@@ -9,7 +9,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.workload: infrastructure
-ms.date: 03/27/2023
+ms.date: 06/22/2023
 ms.author: juergent
 ms.custom: H1Hack27Feb2017
 ---
@@ -59,7 +59,7 @@ When you look up the price list for Azure managed disks, then it becomes apparen
 Since we don't want to define which direction you should go, we're leaving the decision to you on whether to take the single disk approach or to take the multiple disk approach. Though keep in mind that the single disk approach can hit its limitations with the 1,200MB/sec throughput. There might be a point where you need to stretch /hana/data across multiple volumes. also keep in mind that the capabilities of Azure VMs in providing storage throughput are going to grow over time. And that HANA savepoints are extremely critical and demand high throughput for the **/hana/data** volume
 
 > [!IMPORTANT]
-> You have the possibility to define the sector size of Azure Premium SSD v2 as 512 Bytes or 4096 Bytes. All the tests conducted and the certification as storage for SAP HANA were done with a sector size of 4096 Bytes. Therefore, you should make sure that this is the sector size of choice when you deploy disks. This sector size is different than stripe sizes that you need to define when using a logical volume manager.
+> You have the possibility to define the sector size of Azure Premium SSD v2 as 512 Bytes or 4096 Bytes. Default sector size is 4096 Bytes. Tests conducted with HCMT did not reveal any signficant differences in perforamance and throughput between the different sector sizes. This sector size is different than stripe sizes that you need to define when using a logical volume manager.
 
 **Recommendation: The recommended configurations with Azure premium storage for production scenarios look like:**