SAP S/4HANA Administration · SAP HANA Architecture & Persistence

You're modeling a table that is written constantly but almost never read analytically (transient, write-once staging data). Why might row store be the right choice, and how does HANA otherwise soften the write cost of column tables?

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 SAP HANA Architecture & Persistence

You're choosing the replication mode for HANA system replication to a secondary site. What does synchronous buy you, what does it cost, and when would you deliberately choose asynchronous?

A HANA system has hit its memory ceiling on a single host. You can scale up or scale out — what's the difference, and which one is the prerequisite for HA via standby nodes?

Which parameters define where HANA data and log volumes live, and in which file and section?

Your log volume is filling up even though full data backups run nightly. Given how HANA triggers log backups, why?

Why must you never relocate, rename, or delete HANA datafiles with OS commands, even with the database stopped, and what marker warns you?

What hard sizing requirement does an in-memory database (IMDB) like HANA impose that a traditional disk-based database does not?

Start learning today

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