Skip to content

Commit c8578f0

Browse files
authored
Update planning-guide.md
1 parent 7931dce commit c8578f0

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/virtual-machines/workloads/sap/planning-guide.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -446,7 +446,11 @@ Read [this article][vpn-gateway-create-site-to-site-rm-powershell] for more info
446446
>
447447
> The reason for these restrictions is the requirement for a low latency high-performance network within one SAP system, especially between the application instances and the DBMS layer of an SAP system.
448448
>
449-
>
449+
> Special planning of the systems and regions must occur when using multiple SAP systems which are highly integrated. Make sure to deploy these systems as close as possible to each other to minimize network latency. Examples of highly integrated SAP systems are:
450+
> * SAP BW reading data from SAP OLTP systems like ERP or CRM or SRM; or
451+
> * SAP SLT being used to replicate data between multiple SPA systems or even between SAP and non-SAP systems; or
452+
> * SAP S/4 connected to an SAP ERP system; etc.
453+
450454

451455
### Supported OS and Database Releases
452456
* Microsoft server software supported for Azure Virtual Machine Services is listed in this article: <https://support.microsoft.com/kb/2721672>.

0 commit comments

Comments
 (0)