Testing, Debugging & Performance Analysis

SQLScript has no test-driven-development framework. What is the standard best-practice pattern for repeatable tests in the SQL console?

Your AMDP debugger just won't stop at the breakpoint in a SAP BW/4HANA transformation routine. What's the most likely cause?

You set an AMDP breakpoint and its circle is blue, not green. Will execution stop there yet?

You measure a procedure's timing while stepping through it in the AMDP debugger. Can you trust those numbers as production performance?

Same join query, run two ways: an explicit list of 6 columns vs SELECT *. Which is faster on HANA's column store, and roughly by how much?

A HANA plan operator has the prefix BW. Which engine ran it — and why do these prefixes matter for performance?

You run EXPLAIN PLAN FOR <query> and get no result set back. Where did the plan go?

In a PlanViz node, what's the difference between Inclusive Time and Exclusive Time — and what do the edges between nodes tell you?

Why use the SQLSCRIPT_LOGGING library's LOG() instead of just INSERTing into your own log table from a procedure?

What are the two practical drawbacks of the SQLSCRIPT_LOGGING library that make it awkward in real projects?

In the SQLScript end-user test framework, what actually marks a library as tests and a procedure as a test case?

You run CALL SQLSCRIPT_RUN_TESTS_ON_ORIGINAL_DATA(..., ?, ?, ?). What comes back?

In a SQLSCRIPT_TEST assertion, does EXPECT_TABLE_EQ(t1, t2) treat two tables with the same rows in a different order as equal?

Which SQLScript debugger runs where — Eclipse/HANA Studio vs the ABAP world vs Web IDE?

What can the AMDP debugger do that the database-level SQLScript debugger can't — and how do you check it's even available?

You want HANA's built-in static analysis of a SQLScript procedure. Where do the rules live, and which procedure checks brand-new source that isn't created yet?

The UNCHECKED_SQL_INJECTION_SAFETY rule fires on your dynamic SQL. What two kinds of remedy does it accept for the input parameter?

A procedure written on an older HANA reads ::ROWCOUNT right after a SELECT. After upgrading to HANA 2.0 SPS 04, what changes?