HANA Index Server Architecture

At the top is the Connection and Session Management which creates and manages sessions and connections for the database clients such as SAP BusinessObjects Reporting tools or applications.

The Transaction Manager is the component that coordinates transactions, controls transaction isolation and keeps track of running and closed transactions.

The client requests are analyzed and executed by the set of components summarized as Request Processing and Execution Control. Once a session is established, database clients typically use SQL statements to communicate with Request Processing and Executin Control. For analytical applications the multidimensional query language MDX is supported in addition.

Incomming SQL requests are received by SQL Processor. Data manipulation statements are executed by th SQL Processor itself. Other types of requests are delegated to other components.

For example, Data difinition statements, such as definitions of relational tables, columns, views, indexes and Procedures are dispatched to the Metadata Manager.

Planning commands are routed to the Planning Engine that allows financial planning applications to execute basic planning operations in the database layer.

The SAP HANA database offers programming capabilities for running application specifc calculations inside the database system. The SAP HANA database has its own programming languages. SQL Script is used to write database stored procedures. Procedure calls are forwarded to the Stored Procedure processor.

Incoming MDX requests are processed by the MDX engine and also forwarded to the Calc Engine.

Features such as SQLScript, MDX and planning operations are implemented using a common infrastructure call Calc Engine.