Data Tiering: Persistent Memory, NSE & Extension Nodes

In an SAP HANA system with persistent memory, how is data split between DRAM and persistent memory?

In SAP HANA NSE, what is the difference between column-loadable and page-loadable data, and how do you set it?

When modifying persistent-memory settings with ALTER TABLE in SAP HANA, what do the IMMEDIATE, DEFERRED, and CASCADE options do?

Which worker group and host subrole identify an SAP HANA extension node, and why does the worker group matter?

What monitoring views provide buffer-cache statistics in SAP HANA NSE, and how can you identify page-loadable tables?

What are the SAP HANA warm-data tiering options versus the cold-data options?

How is persistent memory enabled when installing SAP HANA, and what does the installer set?

On which four levels can SAP HANA persistent memory be configured, and how is inheritance handled?

What does the SAP HANA NSE advisor do?

When you UNLOAD a table column in SAP HANA, is memory freed by default, and which parameter changes this?

What are the hardware prerequisites for SAP HANA persistent memory?

Which SAP HANA monitoring views report whether a table/column uses persistent memory and its usage?

What is a key limitation on what SAP HANA persistent memory protects against?

For SAP HANA extension-node auto-failover, how must standby nodes be assigned to worker groups?

What is an SAP HANA extension node, and what data does it hold?

Which SAP applications can use SAP HANA dynamic tiering, and which cannot?

What is SAP HANA dynamic tiering, and which tables extend data to its disk-based store?

How are hot, warm, and cold data defined in SAP HANA data tiering, and where is each stored?

What is the default size of the SAP HANA NSE buffer cache, and which parameters set it?

What is SAP HANA Native Storage Extension (NSE), and what does it load instead of columns?

What is the SAP HANA Data Warehousing Foundation's Data Lifecycle Manager used for?

Why is the volatility of DRAM a problem for SAP HANA, and how does persistent memory address it?

How relaxed can the data ratio be on an SAP HANA extension node compared to a standard node?

Why must an SAP HANA extension node's volumes be excluded from table redistribution in a scale-out system?

Which SAP HANA parameter sets the location of persistent-memory storage, and which enables it for the whole database?

What is data aging in SAP HANA, and where is it available?

What is the minimum scale-out setup that uses an SAP HANA extension node, and is a single-node-plus-extension-node a scale-out system?

How do the three SAP HANA storage tiers rank on volume, price, and performance?

After configuring SAP HANA NSE or an extension node, where can you verify table placement / node location?

Why is correct hot/warm data classification critical when using an SAP HANA extension node?

How does SAP HANA Native Storage Extension (NSE) change the total in-memory capacity equation?