Skip to content

Commit 234b126

Browse files
committed
Extend zonal ppg guidance
1 parent 8d1036d commit 234b126

File tree

2 files changed

+1
-1
lines changed

2 files changed

+1
-1
lines changed
-19.7 KB
Loading

articles/sap/workloads/proximity-placement-scenarios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ For more information and deployment examples of proximity placement groups, see
6969

7070
### Proximity placement groups with zonal deployments
7171

72-
It's important to provide a reasonably low network latency between the SAP application tier and the DBMS tier. In most situations, a zonal deployment alone fulfills this requirement. To place VMs as close as possible and enable such a reasonably low network latency for a limited set of scenarios, an Azure proximity placement group can be defined for such an SAP system.
72+
It's important to provide a reasonably low network latency between the SAP application tier and the DBMS tier. In most situations, a zonal deployment alone fulfills this requirement. For a limited set of scenarios, such zonal deployment alone might not meet the application latency requirements. Such situations require VM placement as close as possible and enable such reasonably low network latency, an Azure proximity placement group can be defined for such an SAP system.
7373

7474
Avoid bundling several SAP production or nonproduction systems into a single proximity placement group. Avoid bundles of SAP systems because the more systems you group in a proximity placement group, the higher the chances:
7575

0 commit comments

Comments
 (0)