HANA News Blog
SAP HANA Hyperscaler news 09/2024
Jens Gleichmann • 20. September 2024
News for AWS, GCP and MS Azure

🎯 GCP has certified the first Emerald Rapids SP instances - c4-highmem (2024-08-14)
🎯 MS Azure has certified Msv3 + Mdsv3-series with max. 1792 vCPUs and 30TB RAM (2024-09-02)
🥇 AWS is the leader in the virtualized instance type category
🥇 GCP is the leader in the bare metal instance type category
total by RAM statistic:
1. GCP : x4-megamem-1920-metal: 32.768 GiB
2. MS Azure: M896ixds_32_v3 / M1792ixds_32_v3: 30.400GiB
3. AWS: u7in-24tb.224xlarge: 24.576GiB
🌇 As MS Azure's S-Series (HANA Large Instance service) is in sunset mode, there are no bare metal instances left which you can order.
SAP HANA News by XLC

An inverted individual index is a special type of SAP HANA index which can only cover unique indexes. This includes all primary key structures. Unlike traditional column store indexes on more than one column (inverted value, inverted hash) an inverted individual index (Inv Idv Idx) doesn't need a dedicated concat.

SAP HANA systems may experience high swap usage, hangs, or performance issues when THP (Transparent Huge Pages) is enabled with "madvise". This occurs on multi-NUMA node systems where one or more NUMA nodes are close to full memory usage while others have plenty of free memory, and counters for THP allocations, direct

With SPS06 and even stronger in SPS07 the HEX engine was pushed to be used more often. This results on the one hand side in easy scenario to perfect results with lower memory and CPU consumption ending up in faster response times. But in scenarios with FAE (for all entries) together with FDA (fast data access), it can result in bad performance. After some customers upgraded their first systems to SPS07 I recommended to wait for Rev. 73/74. But some started early with Rev. 71/72 and we had to troubleshoot many statement. If you have similar performance issues after the upgrade to SPS07 feel free to contact us! Our current recommendation is to use Rev. 74 with some workarounds. The performance degradation is extreme in systems like EWM and BW with high analytical workload.

SAP NSE was introduced with HANA 2.0 SPS04 and based on a similar approach like data aging. Data aging based on a application level approach which has a side effect if you are using a lot of Z-coding. You have to use special BADI's to access the correct data. This means you have to adapt your coding if you are using it for Z-tables or using not SAP standard functions for accessing the data in your Z-coding. In this blog we will talk about the technical aspects in more detail.
In transformation projects like SAP RISE / SAP Cloud ERP, the Roles & Responsibilities (R+R) list often serves as the backbone for collaboration between customer, partner, and SAP. Yet too often, this list is treated as a static document rather than a living framework. Sometimes nobody knows exactly what was defined by

In the world of modern database management systems, query performance is not just a matter of hardware—it’s about smart execution plans. At the core of generating these plans lies a critical component: optimizer statistics.
This article explores why databases need optimizer statistics, with particular emphasis on SAP HANA, while drawing parallels with Oracle, Microsoft SQL Server (MSSQL), and IBM DB2.





