Dynamic Tiering: Store Data Efficiently with Data Aging and SAP HANA Native Storage Extension

SAP HANA is a powerful in-memory database that can process large amounts of data in real time. The data is stored in the expensive main memory, which has limited storage capacity. However, not all data needs to be permanently held in main memory. This is where the Dynamic Tiering technologies that SAP has developed in recent years come into play.

Data Aging

Data Aging is an application-level technology that defines and controls which data does not need to remain permanently in main memory. It is stored in separate partitions in SAP HANA using partitioning rules. This allows large amounts of data to be stored more cost-effectively without having to sacrifice speed and availability.

SAP HANA Native Storage Extension (NSE)

Another technology is the SAP HANA Native Storage Extension (NSE), which works on a technical level. Part of the database works with a classic table buffer, which only stores a small part of the data in the main memory. The decision as to which data can be stored in this way varies from customer to customer and must be well planned.

SAP today discourages the use of data aging, as NSE is a more efficient technology. NSE can be used for technical data and logging data within SAP S/4HANA. However, the savings potential versus the additional configuration and administration effort should be critically questioned. After all, the first choice for potential savings in application data remains data avoidance, data archiving and data deletion.

The statutory requirements of the General Data Protection Regulation (DSGVO) must be given special consideration. For the latest information on NSE in connection with SAP S/4HANA, see the following SAP Note:

2816823 – Use of SAP HANA Native Storage Extension in SAP S/4HANA and SAP Business Suite powered by SAP HANA

Overall, dynamic tiering with data aging and SAP HANA Native Storage Extension offers a cost-effective way to manage large volumes of data without having to sacrifice speed and availability. However, individual requirements and legal specifications should be carefully considered during planning and implementation.