SAP HANA 2.0 Administration · Database Objects: Catalog, Views, Procedures & Functions

Column-store INSERTs are slower than row-store. Why is the column store still the default choice for SAP HANA tables?

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: Catalog, Views, Procedures & Functions

You declare a HANA column as FLOAT(n) expecting single-precision storage. At what value of n does HANA silently give you DOUBLE instead of REAL?

Why is VARCHAR the wrong choice for a column that may hold ABAP CHAR data or any non-English text in HANA?

A HANA TIMESTAMP advertises FF7 (7 fractional-second digits, 100 ns). Can you rely on that to distinguish two events microseconds apart?

For a large free-text column that may contain non-English (Unicode) content, which LOB type is correct, and what breaks if you pick CLOB?

A user complains they still can't read a table after you created a public synonym for it. Is the synonym broken?

You need to compute a value inline within a SELECT's column list. Why must that be a function and not a stored procedure?

Start learning today

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