SAP HANA SQLScript · SAP HANA for SQLScript Developers

Why does storing a table by columns make SUM(amount) and single-column filters so much faster than a row store?

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 for SQLScript Developers

Coming from a classic RDBMS, why is pre-building secondary indexes, aggregate tables and materialized views usually the wrong instinct on HANA?

Why does looping over rows one-by-one in your program to compute a total defeat the whole point of HANA?

Why should you avoid naming your own table the same as an object in the HANA public schema?

Two SQL statements sit back-to-back in one SQL console tab with no semicolon between them. You press F8. What happens?

You highlight only the first three lines and press F8. Does table NAMES still exist afterward? ``` CREATE TABLE names (id INT); INSERT INTO names VALUES (1); SELECT * FROM names; DROP TABLE names; ```

You are creating a new business table in HANA. Column store or row store, and why?

Start learning today

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