KEMBAR78
Sap Database | PDF
Scribd
Upload
82 views1 page

Sap Database

The SAP HANA database consists of two database engines: a column-based store optimized for analytical operations on large amounts of aggregated data, and a row-based store optimized for write operations. Tables can be stored in either engine and the engine can be selected when the table is created. The row-store loads tables into memory at startup while the column-store can load tables into memory either at startup or on demand. Both engines share a common layer that provides data persistency and changes are written to persistent storage through automatic savepoints.

Uploaded by

Subramani Sambandam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
82 views1 page

Sap Database

The SAP HANA database consists of two database engines: a column-based store optimized for analytical operations on large amounts of aggregated data, and a row-based store optimized for write operations. Tables can be stored in either engine and the engine can be selected when the table is created. The row-store loads tables into memory at startup while the column-store can load tables into memory either at startup or on demand. Both engines share a common layer that provides data persistency and changes are written to persistent storage through automatic savepoints.

Uploaded by

Subramani Sambandam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

SAP HANA DATABASE

SAP HANA Database The SAP HANA database consists of two database engines: • The
column-based store, storing relational data in columns, optimized for holding data mart tables
with large amounts of data, which are aggregated and used in analytical operations. • The row-
based store, storing relational data in rows. This row store is optimized for write operations and
has a lower compression rate, and its query performance is much lower compared to the column-
based store. The engine that is used to store data can be selected on a per-table basis at the time
of creation of a table (and changed subsequently). Tables in the row-store are loaded into
memory at startup time, whereas tables in the column-store can be either loaded at startup or on
demand, during normal operation of the SAP HANA database.

Both engines share a common persistency layer [6], which provides data persistency across both
engines. Changes to in-memory database pages (equivalent to Oracle blocks) are made persistent
through savepoints written to the data volumes on persistent storage. This is done automatically,
at least every 5 minutes, and this is customizable. Besides, every transaction committed in the
SAP HANA database is persisted by the logger of the persistency layer in a log entry written
synchronously to the log volumes (similar to Oracle redo logs) on persistent storage. The SAP
HANA database supports SQL (JDBC/ODBC), MDX (ODBO), and BICS (SQL DBC). BICS is
a SAP HANA-specific SQL Script language that is an extension to SQL that can be used to push
down data-intensive application logic into the SAP HANA database (similar to Oracle stored
procedures).

You might also like