Database
As a database, SAP HANA is a full, ACID-compliant relational database with standard SQL plus advanced in-memory and analytical capabilities. Understanding it as a database, tables, SQL, transactions, is the basis for modelling and development on HANA.
Knowing HANA as a database, its stores, SQL, and pushdown capabilities, lets you model efficiently and exploit its speed (code-to-data) rather than treating it like a slow traditional database.
- HANA supports standard SQL, transactions (ACID), constraints and the relational model, so it behaves like a database developers…
- You interact via SQL and tools like the HANA cockpit, HANA Studio (older) and the database explorer in BAS.
- Column & row stores for different access patterns.
- Watch out: Treating HANA like a row-store legacy DB.
A capable relational database
HANA supports standard SQL, transactions (ACID), constraints and the relational model, so it behaves like a database developers know, while adding in-memory speed and advanced engines. For S/4HANA it is the single database holding all application data.
Beyond basic relational
- Column & row stores for different access patterns.
- Advanced engines: spatial, graph, text/search, predictive/ML libraries.
- SQLScript & procedures for database-side logic (code pushdown).
- Multitenant containers for isolation.
Working with HANA
You interact via SQL and tools like the HANA cockpit, HANA Studio (older) and the database explorer in BAS. For SAP applications, most access is through the ABAP layer (Open SQL/CDS), but modellers and developers also write native SQL/SQLScript and build calculation views.
Why it matters
Knowing HANA as a database, its stores, SQL, and pushdown capabilities, lets you model efficiently and exploit its speed (code-to-data) rather than treating it like a slow traditional database.
Common pitfalls
- Treating HANA like a row-store legacy DB.
- Not exploiting pushdown (SQLScript/CDS).
- Ignoring the advanced engines when they fit the problem.