What is a valid reason for leveraging SAP HANA Native Storage Extension (NSE) in the SAP BW/4HANA Data Tiering Optimization (DTO) concept?

Question

Options

• ATo move historical data that only needs to be read exceptionally to an external storage.
• BTo reduce the SAP HANA memory consumption of data that is only used infrequently
• CTo improve the reporting performance for current data which is used frequently.
• DTo create an external archive for data, to ensure legal requirements are fulfilled.

• A
  5% (3)
• B
  81% (47)
• C
  3% (2)
• D
  10% (6)

Explanation

B is correct because SAP HANA NSE is specifically designed to offload infrequently accessed ("warm") data from expensive in-memory storage to disk-based persistent storage, while keeping it queryable within the HANA database - directly reducing memory footprint without removing the data from the system.

A is wrong because moving data to an external storage system describes Nearline Storage (NLS), not NSE. NLS handles "cold" data that needs to leave the HANA database entirely. NSE keeps data inside HANA, just on disk rather than in RAM.

C is wrong because NSE reduces performance compared to in-memory storage - it is counterproductive for hot, frequently accessed data. Current, frequently used data should remain fully in-memory for optimal reporting speed.

D is wrong because NSE creates no external archive and fulfills no legal retention requirements on its own. Legal archiving falls under Data Archiving/ILM solutions, which physically remove and externalize records.

Memory tip: Think of DTO as three temperature tiers - Hot (in-memory), Warm (NSE = on-disk but still in HANA), Cold (NLS = outside HANA). NSE is always the middle "warm" tier answer whenever the question mentions reducing memory for infrequent data.

No community discussion yet for this question.