SAP Knowledge Base Article - Preview

2931465 - When to use Proximity Placement Groups on Azure to Reduce Network Latency – 3 Tier NetWeaver or S/4HANA architecture

Symptom

  • A high Bandwidth Low Latency network connection is required between SAP Application Servers and DBMS Server on a single SAP System (single SID)
  • Latency testing tools such as ABAP Meter, TCPPing and NIPING indicate excess latency between SAP Application Servers and DBMS Server
  • High Database times are seen in ST03 but no obvious expensive query can be identified


Read more...

Environment

Three Tier SAP systems running on Azure VMs.  Three Tier SAP systems place the SAP Application layer and DBMS layer on separate VMs.

In all cases the SAP Application Servers and DBMS Servers must be in the same Azure Virtual Network.  The use of subnets within a Virtual Network is supported. It is not supported to have NVAs in the path between the SAP application layer and DBMS layer as documented in 2731110 - Support of Network Virtual Appliances (NVA) for SAP on Azure

Latency between SAP Systems with different SIDs, such as between an ECC system and a BW system are not covered by this SAP Note.  The use of Azure Proximity Placement Groups will not benefit communication between SAP systems.  

Proximity Placement Groups are only useful and applicable to a single SAP SID

Product

SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5

Keywords

Azure proximity placement groups, PPG, /SSA/CAT, ABAPMeter, DB Acc , KBA , BC-OP-NT-AZR , Windows on Microsoft Azure , BC-OP-LNX-AZR , Linux on Microsoft Azure , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.