SAP HANA 2.0 Administration · Instance Administration: Parameters, Memory & Workload

A HANA query hits statement_memory_limit. Is it slowed down, queued, or killed — and why does that design choice matter?

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 Instance Administration: Parameters, Memory & Workload

You created a HANA workload class capping statement memory for the SAP application, but it has no effect on those sessions. What step did you skip?

To cap statement memory and parallelism for a group of statements in HANA, do you use a workload class or a workload mapping — and what does each contribute?

A colleague says HANA log segments hold the database's table data. Correct them — what do log segments actually contain, and why does the distinction matter operationally?

During full-log recovery you move a log volume to a temp file system. Why is a symbolic link at the original path required for the database to start at all?

In M_LOG_SEGMENTS, how many segments per logging service can show state Writing at once, and what does that tell you when diagnosing?

Why does HANA normal log mode enable point-in-time recovery — what specifically does it guarantee that overwrite mode does not?

Start learning today

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