Skip to main content

SAP HANA Architecture

Data is compressed by different compression techniques (e.g. dictionary encoding, run length encoding, sparse encoding, cluster encoding, indirect encoding) in SAP HANA Column store.

When main memory limit is reached in SAP HANA, the whole database objects (table, view,etc.) that are not used will be unloaded from the main memory and saved into the disk.

These objects names are defined by application semantic and reloaded into main memory from the disk when required again. Under normal circumstances SAP HANA database manages unloading and loading of data automatically.

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

SAP HANA Server consists of :

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

SAP HANA Index Server:
SAP HANA Database Main server are index server. Detail of each server is as below-

It's the main SAP HANA database component
It contains actual data stores and the engine for processing the data.
Index Server processes incoming SQL or MDX statement.

SAP HANA Index Server overview

Session and Transaction Manager: Session Component manage 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 (e,g. Analytic View in SAP HANA).

SQL / SQL Script / R / Calc Engine: This Component executes SQL / SQL script and calculation data convert in calculation model.

Repository: Repository maintain the versioning of SAP HANA metadata object e.g.(Attribute view, Analytic View, Stored procedure).

Persistence layer: This layer uses in-built feature "Disaster Recovery" of SAP HANA database. Backup is saved in it as save points in the data volume.

Processor Server:

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




Comments

Post a Comment

Popular posts from this blog

SAP HANA In Memory Strategy

SAP HANA has many processes running on the SUSE Linux Server. SUSE Linux server manages the reservation of memory to all process. When SAP HANA starts up, Linux OS reserves memory for the program code, program stack, and static data. OS can dynamically reserve additional data memory upon request from the SAP HANA Server. SAP HANA create a memory pool for managing and tracking the consumption of memory. The memory pool is used to store all the in-memory data and system tables, thread stack, temporary computations and all other data structure required for managing the database. When more memory is required for table growth or temporary computations, the SAP HANA memory manager obtains this from the pool. For an overview, check out the Memory Overview feature of the SAP HANA studio. To access it, right-click on a System ->Configuration and Monitoring -> Open Memory Overview in the context menu, as follows:
Post a Comment
Read more

SAP HANA Advantages

Below are advantages of SAP HANA - By In-Memory Technology user can explore and analyze all transaction and analytic data in real time from virtually any data source. Data can be aggregated from many sources. Real-time replication services can be used to access and replicate data from SAP ERP. SQL and MDX interface from third party support. It provides information modeling and design environment.
Post a Comment
Read more