HANA News Blog

Smart SAP HANA Optimization: Applying NSE for Better Efficiency

Matthias Sander • 15. Januar 2025

Optimize your HANA with NSE

 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

The Results:  Memory Savings 1135 GB


  • NSE: 945 GB saved
  • Changing one table to Inverted Individual Index: 90 GB saved
  • SBCMCONT1 cleanup: 230 GB saved
  • Offset: NSE Buffer Cache (130 GB)


As you can see, we have not only saved memory through NSE, but have also discovered other potential savings in the course of the project.


Including the NSE buffer cache, we were able to save around 48% of the memory compared to the initial situation. A really great result. On average, we achieve savings of around 25-35% for an ERP system.

After the GoLive of NSE, the client waited around 5 weeks until the database memory was reduced from 4 TB to 2.5 TB, despite prior and intensive tests in the test system.

As a result, we achieved optimal sizing according to SAP:

  • 50 % payload data
  • 50 % working memory



It would have been possible to reduce the memory to 2 TB, but then we would have been directly at an utilization of 62%. Depending on the growth and use of the database, this may already be too much and it would have to be increased again soon.

The customer has decided on a conservative approach and selected 2.5 TB.   

Beyond NSE: Holistic Data Management Is Key

While NSE delivered exceptional results in this case, it is not the only solution for optimizing SAP HANA systems. Proactive data archiving and, importantly, data deletion can also lead to significant memory savings. For example, SAP note "2388483 - How-To: Data Management for Technical Tables" provides excellent strategies for managing technical tables effectively.

These steps — NSE, archiving, and deletion — serve as excellent preparation for:


  • Purchasing new on-premise hardware
  • Migrating to cloud or other cloud environments
  • Transitioning to SAP RISE

The less data you store in memory, the lower your costs and environmental impact. These optimizations not only improve performance but also contribute to a greener IT landscape by reducing energy usage. It is better to clean up first and then migrate.

As you can see from this story, an NSE project helps you to get to know your data better and also reveals other areas where memory can be saved.

How Can We Help? If you’re considering memory optimization for your SAP HANA system we’re here to help. Feel free to reach out with any questions or to explore how we can assist you in unlocking the full potential of your SAP HANA environment.


Together, let’s make SAP HANA smarter, leaner, and more sustainable.

SAP HANA News by XLC

von Jens Gleichmann • 27. Oktober 2026
The topic of HANA performance is one of the most discussed topics in nearly every single SAP project we are involved. Performance has always been an important aspect in general; however, particularly when switching databases or application releases - whether moving from anyDB to HANA or, more specifically, from ERP on
Orientation in DMO scenarios
von Dominik Fiedler • 21. Oktober 2026
There are multiple DMO scenarios and use cases. We heard of many confusions and mixed up statements which we want to order: SUM can not only update software components, but can also execute a database migration (for ABAP based systems)
DMOVE2S4 and Homogeneous option for SAP SUM DMO
von Jens Gleichmann • 21. Oktober 2026
DMO used to be heterogeneous (change of DB). Now you can use DMO with system move (also on-prem to target on-prem) to migrate and convert ECC on HANA to S/4 or just update/upgrade S/4 and move it to another location like other DC or other instance in one step. The DMOVE2S4 is just to move and convert to the cloud in one step. This includes also anyDB source systems and downtime-optimization techniques (doDMO and doC).
von Dominik Fiedler • 7. August 2026
SAP HANA Monitoring Views Cheat Sheet
HANA OS maintenance
von Jens Gleichmann • 27. Juli 2026
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.
von Jens Gleichmann • 14. April 2026
KVM as alternative with low TCO
inverted individual index is a special type of SAP HANA index wich can save memory
von Jens Gleichmann • 6. April 2026
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.
Total NSE savings
von Jens Gleichmann • 5. April 2026
This blog presents the results of a customer case which can be used as a reference for other implementations
SAP HANA performance issues with THP on multi-NUMA node systems
von Jens Gleichmann • 30. März 2026
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
Transparent Huge Pages (THP) with madvise can trigger high swap usage and performance issues
von Matthias Sander • 26. Januar 2026
Transparent Huge Pages (THP) with madvise can trigger high swap usage, performance issues, or even system hangs on multi-NUMA systems.
more