SAP HANA 2.0 Administration · Data Tiering: Persistent Memory, NSE & Extension Nodes

Data aging and NSE both reduce HANA's memory footprint. What kind of mechanism is data aging, and what bounds where you can use it?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Data Tiering: Persistent Memory, NSE & Extension Nodes

A team expects persistent memory to speed up their write-heavy HANA workload. Why is that the wrong expectation, and what does the DRAM/PMEM split actually optimize?

A customer wants to add persistent memory to an existing HANA appliance with DRAM populated on only some channels. Which prerequisites block this, and which one is the easy-to-miss planning trap?

You run ALTER TABLE ... PERSISTENT MEMORY on a large partitioned HANA table during business hours. Which option avoids an immediate cost spike, and what does CASCADE change that the others don't?

You set PERSISTENT MEMORY ON at the table level but want one column excluded. Does HANA's level hierarchy allow that, and what does DEFAULT actually mean?

What is the one defining property of HANA Native Storage Extension (NSE) that distinguishes it from normal column loading, and why does it shrink the memory footprint?

You're deciding whether a large rarely-queried column should be COLUMN LOADABLE or PAGE LOADABLE in HANA NSE. What's the single trade-off, and how risky is getting it wrong?

Start learning today

Free to start — download the app or use it in your browser.