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
@@ -52,6 +52,7 @@ SAP HANA on Azure (Large Instances) service based on Revision 4 stamps is availa
52
52
| Optimized for OLTP: SAP Business Suite<br /> on SAP HANA or S/4HANA (OLTP),<br /> generic OLTP | SAP HANA on Azure S72m<br /> – 2 x Intel® Xeon® Processor E7-8890 v3<br /> 36 CPU cores and 72 CPU threads | 1.5 TB | 6 TB | Not offered anymore |
53
53
|---| SAP HANA on Azure S144m<br /> – 4 x Intel® Xeon® Processor E7-8890 v3<br /> 72 CPU cores and 144 CPU threads | 3.0 TB | 12 TB | Not offered anymore |
54
54
|---| SAP HANA on Azure S192m<br /> – 4 x Intel® Xeon® Processor E7-8890 v4<br /> 96 CPU cores and 192 CPU threads | 4.0 TB | 16 TB | Not offered anymore |
55
+
| --- | SAP HANA on Azure S224m<br /> – 4 x Intel® Xeon® Platinum 8276 processor (also known as Cascade lake)<br /> 112 CPU cores and 224 CPU threads | 6.0 TB | 10.5 TB | Available in Revision3 and Revision4 stamps |
55
56
|---| SAP HANA on Azure S384m<br /> – 8 x Intel® Xeon® Processor E7-8890 v4<br /> 192 CPU cores and 384 CPU threads | 6.0 TB | 18 TB | Available in Revision4 stamps|
56
57
|---| SAP HANA on Azure S384xm<br /> – 8 x Intel® Xeon® Processor E7-8890 v4<br /> 192 CPU cores and 384 CPU threads | 8.0 TB | 22 TB | Available in Revision4 stamps |
57
58
|---| SAP HANA on Azure S576m<br /> – 12 x Intel® Xeon® Processor E7-8890 v4<br /> 288 CPU cores and 576 CPU threads | 12.0 TB | 28 TB | Available in Revision4 stamps|
@@ -87,7 +88,7 @@ The specific configurations chosen are dependent on workload, CPU resources, and
87
88
88
89
The hardware base for the offers, except units for customer-specific sizing projects, are SAP HANA TDI-certified. Two different classes of hardware divide the SKUs into:
89
90
90
-
- S72, S72m, S96, S144, S144m, S192, S192m, S192xm, and S224, which are referred to as the "Type I class" of SKUs.
91
+
- S72, S72m, S96, S144, S144m, S192, S192m, S192xm, S224, and S224m which are referred to as the "Type I class" of SKUs.
91
92
- S384, S384m, S384xm, S384xxm, S576m, S576xm S768m, S768xm, and S960m, which are referred to as the "Type II class" of SKUs.
92
93
- If you are interested in other S224 SKUs offering from 4.5TB to 9TB with Optane, contact your Microsoft account team to get more information.
@@ -35,7 +35,7 @@ Several common definitions are widely used in the Architecture and Technical Dep
35
35
Domain users of the on-premises domain can access the servers and run services on those VMs (such as DBMS services). Communication and name resolution between VMs deployed on-premises and Azure-deployed VMs is possible. This scenario is typical of the way in which most SAP assets are deployed. For more information, see [Azure VPN Gateway](../../../vpn-gateway/vpn-gateway-about-vpngateways.md?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json) and [Create a virtual network with a site-to-site connection by using the Azure portal](../../../vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-portal.md?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json).
36
36
-**Tenant**: A customer deployed in HANA Large Instance stamp gets isolated into a *tenant.* A tenant is isolated in the networking, storage, and compute layer from other tenants. Storage and compute units assigned to the different tenants can't see each other or communicate with each other on the HANA Large Instance stamp level. A customer can choose to have deployments into different tenants. Even then, there is no communication between tenants on the HANA Large Instance stamp level.
37
37
-**SKU category**: For HANA Large Instance, the following two categories of SKUs are offered:
38
-
-**Type I class**: S72, S72m, S96, S144, S144m, S192, S192m, S192xm, and S224
38
+
-**Type I class**: S72, S72m, S96, S144, S144m, S192, S192m, S192xm, S224, and S224m
39
39
-**Type II class**: S384, S384m, S384xm, S384xxm, S576m, S576xm, S768m, S768xm, and S960m
40
40
-**Stamp**: Defines the Microsoft internal deployment size of HANA Large Instances. Before HANA Large Instance units can get deployed, a HANA Large Instance stamp consisting out of compute, network, and storage racks need to be deployed in a datacenter location. Such a deployment is called a HANA Large instance stamp or from Revision 4 (see below) on we use the alternate of term of **Large Instance Row**
41
41
-**Revision**: There are two different stamp revisions for HANA Large Instance stamps. These differ in architecture and proximity to Azure virtual machine hosts
0 commit comments