SAP HANA SQLScript · Database Objects: Tables, Views, Sequences, Triggers

Why can a join between a ROW-store table and a COLUMN-store table cost more than expected?

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 Database Objects: Tables, Views, Sequences, Triggers

A view is called a "virtual table." What does it actually store, and what's the point of it?

A parameterized view's parameters all have default values. Can you call it as SELECT * FROM v;?

You mark a column PRIMARY KEY, then also add NOT NULL and UNIQUE to the same column. What is redundant?

A table has UNIQUE(a, b). You insert (NULL, 5) and then (NULL, 5) again. What happens?

You run a bare CREATE TABLE (no ROW or COLUMN keyword) on HANA 2.0 SPS 02, then the same statement on SPS 03. Do you get the same storage type?

You must process millions of rows but read only 3 of the table's 40 columns. ROW store or COLUMN store?

Start learning today

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