SAP HANA 2.0 Administration · Performance Analysis: SQL Tuning & Plan Analysis

A statement is slow and its plan's EXECUTION_ENGINE column shows the work bouncing between different HANA engines. What does that signal, and what's the tuning lever?

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 Performance Analysis: SQL Tuning & Plan Analysis

You open PlanViz on a slow statement and want the fastest read on where the time went. Where do you look first, and what does it tell you?

A specific SQL statement from a packaged app (source you can't edit) consistently picks a bad plan. You want a fix that survives recompiles and needs no code change. Statement hint or explicit hint, and what decides?

Your query against M_SYSTEM_DATA_STATISTICS to survey statistics across all tables returns an error instead of a result set. Why, and what's the constraint you missed?

An incident happened 2 weeks ago and you go to M_LOAD_HISTORY_* for the load picture. Why might the data already be gone, and what's the danger of tightening the sampling to catch more?

A junior admin reads an SAP HANA execution plan top-to-bottom and concludes the first listed operator runs first. Why is that backwards, and how is the true order reconstructed?

After a failover to the secondary host, you open M_LOAD_HISTORY_HOST/SERVICE to investigate the pre-failover load and they're empty. Is the history lost, and where do you actually look?

Start learning today

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