SAP HANA SQLScript · Arrays, Dynamic SQL, Exceptions & Transactions

A logging procedure ends with a COMMIT so its log row is definitely saved. It's called in the middle of a big multi-step transaction. What just went wrong?

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 Arrays, Dynamic SQL, Exceptions & Transactions

Inside a procedure you run a dynamic SELECT with EXECUTE IMMEDIATE (no INTO). You then try to use its rows later in the code. Why can't you?

You build dynamic SQL that selects from a local table variable :lt_tmp. You try to concatenate :lt_tmp into the statement string the way you do for a scalar id. What breaks, and what's the fix?

Before HANA 2.0 SPS 04, a read-only SAP BW transformation marked READS SQL DATA couldn't use dynamic SQL at all. Why, and what changed?

You want an error-log row to persist even if the calling transaction later rolls back. What block do you wrap the INSERT in, and what happens at the block's end?

Inside a BEGIN AUTONOMOUS TRANSACTION block you try to CALL another procedure and assign a table variable. Why does this fail, and what's the deadlock trap?

Can you raise a built-in SQL error like 304 (division by zero)? What codes may SIGNAL use, and what does it populate?

Start learning today

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