HANA News Blog

SAP HANA 2.0 SPS08 Roadmap

Jens Gleichmann • 6. Dezember 2024

The latest features of HANA 2.0 *updated*

The roadmap via Road Map Explorer was recently updated and some interesting features jumped into the spotlight. Some of them are already known because they are already implemented in HANA 4.0 (HANA Cloud). SAP HANA 2.0 SPS08 was released at the end of November 2024.


The interesting topics with important changes are: partitioning, data tiering (NSE), security, optimizer, backup and XSA. No, you won't hear any machine learning or AI features from me. If you really want and need them, because there are some, please go to Road Map Explorer :)

Partitioning


  • Support for a generated column as a partitioning key
  • Support for heterogeneous HASH-RANGE partitioning

=> currently HASH-RANGE was only possible for non-heterogeneous / homogeneous partitioning, so it was not possible to use the dynamic range interval option - a great one!


  • Support heterogeneous partitioning into three levels for the following partitioning types:
  • RANGE-RANGE-HASH
  • RANGE-RANGE-RANGE

=> some of you may noticed that some monitoring views in SPS07 already containing some level 3 partition details

=> I'm curious to find a business case for this partition designs

© 2024 SAP SE or an SAP affiliate company. All rights reserved.

Data Tiering - NSE


  • Automatic setting of the minimum-required buffer cache size of the native storage extension, as per persistence size
  • Calculate and set the UNLOAD_THRESHOLD parameter size of the buffer cache automatically based on the persistence size for data in SAP HANA native storage extension

=> SAP mean the parameter buffer_cache_cs - unload_threshold which is set by default to 80 (%)

=> Currently I don't know if this feature helps customers to size the buffer cache properly


  • Dynamic aging for range partitions to native storage extension
  • Enable for dynamic creation of a new range partition, assignment of the load unit "page-loadable" to all range partitions with a certain distance to the new partition

=>  I'm really excited to test this feature, because it will make the life of a DBA easier, if you are using NSE on partition level


  • Provide a transparent switch between column-loadable and page-loadable data without converting the persistency format
  • Significantly reduce conversion time between page-loadable and column-loadable data and, thereby, reduce business downtime and greatly simplify administration for native storage extension

=> this will make the implementation of NSE faster and easier due to lower downtimes - great feature!


© 2024 SAP SE or an SAP affiliate company. All rights reserved.

Optimizer


  • Cache different SQL execution plans based on parameter values that cause variant SQL execution plans for HEX

=> this one of my most anticipated feature, because the HEX or more precise the optimizer made a lot of trouble in the past due to switching engines and the eviction of HEX plans

=> to be able to use multiple plans at a time depending on the bind variables can be a game changer in terms of performance using the HEX

=> this feature is already available since Q2 of 2024 for HANA Cloud named as SQL Plan Advisor

Source: Youtube: What’s New in SAP HANA Cloud | June 2024 | Susen Poppe and Product Experts

Security


  • Extend support for persistence, log, and backup encryption algorithms to AES 256 CTR
  • Activate TLS version 1.3 protocol by default for SQL connections for SAP HANA version 2.0 SPS 08
  • IP-based connect restriction for user groups: Ability to limit access for all users or parts of the user base, for instance, to enable only administrators to log in from the company’s IP range

=> Activating TLS 1.3 by default can create some trouble for some customers, but the implementation was more than necessary after this long time

=> the IP-based connect restriction allows to implement a SoD (Segregation of duties) concepts or helps to isolate instances

© 2024 SAP SE or an SAP affiliate company. All rights reserved.

XSA


  • Improve setup of SAP HANA, extended application services, advanced model behind a reverse proxy
  • Make the solution more robust, especially during system replication takeover, as functionality of the internal system is not dependent on the external route and internal requests are “short-circuited”
  • Enable users to log in from external and internal software
  • Separate networks and DNS zones of external and internal domains
  • Hide internal back-end ports from public access by exposing the external app end points only (for example, to the public Internet) using reverse proxies

=> I'm waiting for such a feature for the "normal" HANA not only for XSA


Backup


  • Setting local secure store (LSS) as the default secure store
  • If LSS is used, inclusion of all necessary secure store backups in SAP HANA backups, eliminating the need to maintain secure store backups explicitly

=> to set LSS as default can also create some trouble and should be implemented carefully


At the end really useful features. I hope that they implement some new monitoring views for NSE and partitioning - otherwise we (XLC) can implement our own solution to get the needed information collected in own history views for our customers. Due to the lack of events around the topic HANA it was not possible to provide the needed feedback for so many customers. The consequence? A lot of missing features which SAP is not aware of. Yes, there is an idea/influence page but without enough votes you can not reach your goal even if the idea is brilliant, because SAP is not aware of the need.   


SAP HANA News by XLC

Why Databases Need Optimizer Statistics – With a Focus on SAP HANA
von Jens Gleichmann 28. Mai 2025
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.
HANA OS maintenance
von Jens Gleichmann 27. Mai 2025
Please notice that when you want to run HANA 2.0 SPS07, you need defined OS levels. As you can see RHEL7 and SLES12 are not certified for SPS07. The SPS07 release of HANA is the basis for the S/4HANA release 2023 which is my recommended go-to release for the next years. Keep in mind that you have to go to SPS07 when you are running SPS06 because it will run out of maintenance end of 2023.
HANA performance degradation after upgrade to SPS07+SPS08
von Jens Gleichmann 27. Mai 2025
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.
The HANA Optimizer is one of the core components of the HANA database. It determines how SQL is exec
von Jens Gleichmann 25. Mai 2025
A database optimizer behaves similarly to the navigation system in your car. You use various parameters to determine which route you want to take to reach a particular destination. Potential additional costs for tolls and ferries also play a role, as do other limitations such as the vehicle's height, length, and width. From these input parameters, the navigation system determines the optimal route based on current traffic information (traffic volume, construction sites, congestion, accidents, closures, etc.), weather conditions, and the length of the route. This means that with exactly identical input parameters, different routes, costs, and thus different travel times can arise depending on the given conditions.
Is NSE worth the effort or is the better question: Do you know your cost per GB of RAM?
von Jens Gleichmann 18. April 2025
Most of our presentations on data tiering projects end with these typical questions: How much we will save? How fast can it be implemented? Is the effort worth it over time? My counter question: "Do you know how much 1 GB of memory costs your company per month or year?" => how much memory we have to save to be beneficial?
Buch: SAP HANA Deepdive
von Jens Gleichmann und Matthias Sander 30. März 2025
Unser erster Buch mit dem Titel "SAP HANA Deepdive: Optimierung und Stabilität im Betrieb" ist erschienen.
More time to switch from BSoH to S/4HANA
von Jens Gleichmann 7. Februar 2025
Recently handelsblatt released an article with a new SAP RISE option called SAP ERP, private edition, transition option. This option includes a extended maintenance until the end 2033. This means 3 years more compared to the original on-prem extended maintenance. This statement was confirmed by SAP on request of handelsblatt, but customers receive more details, such as the price, in the first half of the year. This is a quite unusual move of SAP without any official statement on the news page. Just to raise more doubts? Strategy? However a good move against the critics and the ever shorter timeline. Perhaps it is also a consequence of the growing shortage of experts for operating and migrating the large number of systems.
Optimize your SAP HANA with NSE
von Matthias Sander 15. Januar 2025
When it comes to optimizing SAP HANA, the balance between performance and cost efficiency is critical. I am happy to share a success story where we used the Native Storage Extension (NSE) to significantly optimize memory usage while being able to adjust the sizing at the end. The Challenge: Our client was operating on a 4 TB memory SAP HANA system, where increasing data loads were driving up costs and memory usage. They needed a solution to right-size their system without compromising performance or scalability. The client wanted to use less hardware in the future. The Solution: We implemented NSE to offload less frequently accessed data from memory. The activation was customized based on table usage patterns: 6 tables fully transitioned to NSE 1 table partially transitioned (single partition) 1 table transitioned by specific columns
SAP HANA NSE - a technical deepdive with Q&A
von Jens Gleichmann 6. Januar 2025
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.
The SAP Enterprise Cloud Services Private Cloud Customer Center (PC3) - a new digital delivery
von Jens Gleichmann 5. Januar 2025
The SAP Enterprise Cloud Services Private Cloud Customer Center (PC3) - a new digital delivery engagement model dedicated to manage service delivery for RISE with SAP S/4HANA Cloud, private edition customers.
more