SAP HANA Architecture

Data is pack together by different compression techniques in SAP HANA Architecture. For example cluster encoding, run-length encoding, sparse encoding, dictionary encoding and also indirect encoding.

When the main memory maximum is reached in SAP HANA, the whole database objects for instance table, view etc. However, those are not in use will be unloaded from the main memory and save into the disk.

Therefore these objects names are defined by application semantic and reload into main memory from the disk when requiring again. Under normal circumstances, SAP HANA database manages unloading and loading of data automatically.

However, the user can load and unload data from the individual table manually. Subsequently by selecting a table in SAP HANA studio in respective Schema- by right-clicking and selecting the option “Unload/Load”.

SAP HANA Server consists

  1. Index Server
  2. Preprocessor Server
  3. Name Server
  4. Statistics Server
  5. XS Engine

SAP HANA Index Server

SAP HANA Database Main servers are index server. Detail of each server is as below

Firstly it’s the main SAP HANA database component.

Secondly, it contains actual data stores and the engine for processing the data.

Index Server processes incoming SQL or MDX statement.

  • Session and Transaction Manager

Session Component manages sessions and connections for SAP HANA database. Transaction Manager coordinates and control transactions.

  • SQL and MDX Processor

SQL Processor component queries data and send to them in query processing engine i.e. SQL/SQL Script / R / Calc Engine. MDX Processor queries and manipulates Multidimensional data. For example Analytic View in SAP HANA.

  • SQL / SQL Script / R / Calc Engine

This Component executes SQL / SQL script and calculation data convert in the calculation model.

  • Repository

Repository maintains the versioning of SAP HANA metadata object For instance Attribute view, Analytic View, Store procedure.

  • Persistence layer

During this layer uses the in-built feature “Disaster Recovery” of SAP HANA database. Similarly, backup is saved in it as save points in the data volume.

  1. Preprocessor Server

Meanwhile, this server is used in Text Analysis and extracts data from a text when the search function is used.

  1. Name Server

Moreover, this Server contains all information about the system landscape. In distribute server, the name server contains information about each running component and location of data on the server. This server contains information about the server on which data exists.

  1. Statistic Server

Statistic server is responsible for collecting the data relate to status, resource allocation/consumption and performance of SAP HANA system.

  1. XS Server

XS Server contains XS Engine. It allows external application and developers to use SAP HANA database via the XS Engine client. The external client application can use HTTP to transmit data via XS engine for HTTP server.

})