SAP HANA Interview Questions And Answers

Q1) What is the part of the transaction administrator and session?

Ans: The exchange chief co-ordinates database exchanges and keeps a record of running and shut transactions.  When the exchange is moved back or submitted, the exchange supervisor informs the included stockpiling motors about the occasion so they can run essential activities.

Q2) Clarify how you can maintain a strategic distance from un-vital logging data from being put away?

Ans: You can maintain a strategic distance from un-vital logging data from being put away by delaying the replication by halting the blueprint related occupations.

Q3) Define the Five-minute rule?

Ans: It is a rule of thumb for deciding whether a data item should be kept in memory, or stored on disk and read back into memory when required. The rule is “randomly accessed disk pages of a cache are re-used every 5 minutes”.

Q4) Define Stall?

Ans: Waiting for data to be loaded from the main memory into the CPU cache is called Stall.

Q5) Describe SAP HANA Database Architecture in brief?

Ans: The SAP HANA database is developed in C++ and runs on SUSE Linux Enterprise Server. IT consists of multiple servers and the most important component is the Index Server. It consists of Index Server, Name Server, Statistics Server, Pre-processor Server, and XS Engine. 


Want to analyze business operations which are based on Big Data, enroll in our SAP HANA Training

Index Server

Persistence Layer

The database persistence layer is responsible for the durability and atomicity of transactions. It ensures that the database can be restored to the most recent committed state after a restart and that transactions are either completely executed or completely undone.

Preprocessor Server

The index server uses the preprocessor server for analyzing text data and extracting the information on which the text search capabilities are based.

Name Server

It owns the information about the topology of the SAP HANA system. In a distributed system, it knows where the components are running and which data is located on which server.

Statistic Server

The statistics server collects information about status, performance, and resource consumption from the other servers in the system.. The statistics server also provides a history of measurement data for further analysis.

Session and Transaction Manager

The Transaction manager coordinates database transactions, and keeps track of running and closed transactions. When a transaction is committed or rolled back, the transaction manager informs the involved storage engines about this event so they can execute necessary actions.

XS Engine

XS Engine is an optional component. Using XS Engine clients can connect to the SAP HANA database to fetch data via HTTP.


SAP HANA Tutorials

For in-depth knowledge on SAP HANA, click on below