Skip to content

Commit 257d03d

Browse files
committed
change h2
1 parent d7a69b1 commit 257d03d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-netapp-files/application-volume-group-considerations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ This article describes the requirements and considerations you need to be aware
4444
* Extension 1 supports [availability zone volume placement](use-availability-zones.md) as the new default method for placement. This upgrade mitigates the need for AVset pinning and eliminates the need for proximity placement groups. With support for availability zone volume placement, you only need to select the same availability zone as the database servers. Using availability zone volume placement aligns with the Microsoft recommendation on how to deploy SAP HANA infrastructures to achieve best performance with high-availability, maximum flexibility, and simplified deployment.
4545
If regions do not support availability zones, you can select a regional deployment or choose proximity placement groups.
4646

47-
## Best practices about proximity placement groups
47+
## Best practices about proximity placement
4848

4949
To deploy SAP HANA volumes using the application volume group, you need to ensure that your HANA database VMs and the Azure NetApp Files resources are in close proximity to ensure lowest possible latency. You can achieve close proximity using either of the following deployment methods:
5050

0 commit comments

Comments
 (0)