You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/workloads/sap/planning-guide.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -446,7 +446,11 @@ Read [this article][vpn-gateway-create-site-to-site-rm-powershell] for more info
446
446
>
447
447
> 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.
448
448
>
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
+
450
454
451
455
### Supported OS and Database Releases
452
456
* Microsoft server software supported for Azure Virtual Machine Services is listed in this article: <https://support.microsoft.com/kb/2721672>.
0 commit comments