Database layer in SAP architecture

Database layer

The database layer is where all SAP data physically lives, every master record, transaction document and configuration setting. In S/4HANA this layer is SAP HANA, an in-memory database, which fundamentally changed SAP’s capabilities.

Quick answer

Because all state lives here, the database is the single most important component for performance, sizing, backup and availability, as it is in the installation and administration modules.

Key takeaways

A single database stores everything: application data, the ABAP dictionary (table definitions), and the programs themselves.
Older SAP systems ran on disk-based databases (Oracle, DB2, SQL Server, MaxDB) optimised for either transactions or analytics.
SAP abstracts the database behind the ABAP Dictionary: tables, data elements and domains are defined in SAP and mapped to the…
Watch out: Ignoring database sizing, the top performance constraint.

What the database layer holds

A single database stores everything: application data, the ABAP dictionary (table definitions), and the programs themselves. The application layer reads from and writes to it constantly, so database performance and integrity dominate the whole system’s behaviour.

Traditional databases vs HANA

Older SAP systems ran on disk-based databases (Oracle, DB2, SQL Server, MaxDB) optimised for either transactions or analytics. S/4HANA runs exclusively on HANA, which keeps data in memory and column stores, so it handles transactions and analytics on the same data in real time, eliminating many aggregate tables and separate reporting systems.

The data dictionary

SAP abstracts the database behind the ABAP Dictionary: tables, data elements and domains are defined in SAP and mapped to the underlying database. This is why developers work with logical table definitions rather than raw database DDL.

Why it is the critical tier

Because all state lives here, the database is the single most important component for performance, sizing, backup and availability, as it is in the installation and administration modules.

Common pitfalls

Ignoring database sizing, the top performance constraint.
Assuming any database for S/4HANA, it requires HANA.
Bypassing the dictionary with raw DB changes.

Practice challenge

+0 XPStreak ×0

Question 1 of 3

Which statement is true of Database layer?

Frequently asked questions

What does the term Database layer refer to in SAP?

What reporting depends on Database layer?

Older SAP systems ran on disk-based databases (Oracle, DB2, SQL Server, MaxDB) optimised for either transactions or analytics.

What is the practical takeaway on Database layer?

Because all state lives here, the database is the single most important component for performance, sizing, backup and availability, as it is in the installation and administration modules.

What tends to go wrong with Database layer?

Ignoring database sizing, the top performance constraint. Assuming any database for S/4HANA, it requires HANA. Bypassing the dictionary with raw DB changes.