SAP HANA 2.0 Administration · Table Internals: Stores, Compression, Partitioning & MVCC

A system-versioned table looks like one table, but physically it isn't. How is it really structured, and what is the operational consequence for the history?

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 Table Internals: Stores, Compression, Partitioning & MVCC

A row-store table has a single-column integer sequence key; another has a composite character key. Which gets plain BTREE and which gets CPBTREE, and why does that make CPBTREE the de-facto default for SAP?

A developer assumes the delta store is a throwaway write cache that's cleared on merge. Why is that wrong, and what actually degrades if merges are skipped?

A column table is merging too often during a bulk load. A junior DBA proposes editing auto_merge_decision_func in indexserver.ini. What's the correct response, and what should be done instead?

A delta is dangerously large and a hard merge is stuck waiting. You consider a forced merge. What does FORCED_MERGE do that a hard merge does not, and why is that exactly the risk?

A DBA reads 'merge waiting for token' and concludes the merge is hung. What do merge tokens actually limit, and why is the waiting normal?

Memory merge cuts I/O during chunked loads. What asymmetric cost do you accept, and what has to recover the data if that cost is realised?

Start learning today

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