35+ Tricky SAP HANA Interview Questions with SMART ANSWERS
SAP HANA Interview Questions and Answers

35+ Tricky SAP HANA Interview Questions with SMART ANSWERS

Last updated on 03rd Jul 2020, Blog, Interview Questions

About author

Ananthan (Sr SAP Director )

Highly Expertise in Respective Industry Domain with 10+ Years of Experience Also, He is a Technical Blog Writer for Past 4 Years to Renders A Kind Of Informative Knowledge for JOB Seeker

(5.0) | 17212 Ratings 18461

SAP HANA is the next generation Enterprise Resource Planning (ERP) software that consists of several modules including Production Planning (PP), Materials Management (MM), Financial Accounting and Controlling (FICO), etc. If you are preparing for SAP HANA job interviews to build a career in this domain then this is the right place for you. This SAP HANA interview questions blog is mainly curated to get you acquainted with the type of questions that you might encounter in your job interview

1) Mention what is SAP HANA?


SAP HANA stands for High Performance Analytical Appliance- in-memory computing engine. HANA is linked to ERP systems; Frontend modeling studio can be used for replication server management and load control.

2) Mention the two types of Relational Data stored in HANA?


The two types of relational data stored in HANA includes

  • Row Store
  • Column Store

3) Mention what is the role of the persistence layer in SAP HANA?


SAP HANA has an in-memory computing engine and access the data straightaway without any backup. To avoid the risk of losing data in case of hardware failure or power cutoff, persistence layer comes as a savior and stores all the data in the hard drive which is not volatile.

4) Mention what is modeling studio?


Modeling studio in HANA performs multiple task like

  • Declares which tables are stored in HANA, first part is to get the meta-data and then schedule data replication jobs
  • Manage Data Services to enter the data from SAP Business Warehouse and other systems
  • Manage ERP instances connection, the current release does not support connecting to several ERP instances
  • Use data services for the modeling
  • Do modeling in HANA itself
  • essential licenses for SAP BO data services

5) Mention what are the different compression techniques?


There are three different compression techniques

  • Run-length encoding
  • Cluster encoding
  • Dictionary encoding

6) Mention what is latency?


Latency is referred to the length of time to replicate data from the source system to the target system.

7) Explain what is transformation rules?


Transformation rule is the rule specified in the advanced replication setting transaction for the source table such that data is transformed during the replication process.

8) Mention what is the advantage of SLT replication?


  • SAP SLT works on trigger based approach; such approach has no measurable performance impact in the source system
  • It offers filtering capability and transformation
  • It enables real-time data replication, replicating only related data into HANA from non-SAP and SAP source systems
  • It is fully integrated with HANA studios
  • Replication from several source systems to one HANA system is allowed, also from one source system to multiple HANA systems is allowed.

9) Explain how you can avoid un-necessary information from being stored?


To avoid un-necessary information from being stored, you have to pause the replication by stopping the schema-related jobs

10) Mention what is the role of master controller job in SAP HANA?


The job is arranged on demand and is responsible for

  • Creating database triggers and logging table into the source system
  • Creating Synonyms
  • Writing new entries in admin tables in SLT server when a table is replicated/loaded

11) Explain what happens if the replication is suspended for a longer period of time or system outage of SLT or HANA system?


If the replication is suspended for a longer period of time, the size of the logging tables increases.

12) Mention what is the role of the transaction manager and session?


The transaction manager co-ordinates database transactions and keeps a record of running and closed transactions. When transaction is rolled back or committed, the transaction manager notifies the involved storage engines about the event so they can run necessary actions.

13) Explain how you can avoid un-necessary logging information from being stored?


You can avoid un-necessary logging information from being stored by pausing the replication by stopping the schema-related jobs.

14) What are the components comprising SAP HANA technology?


SAP HANA is a technology that is a collection of different tools and technologies that work in tandem to bring it in existence. There are four technologies which collectively make SAPA HANA:

  • SAP HANA DB: It is the core in-memory database which is central to the functioning of SAP HANA.
  • SAP HANA Studio: It has the modeling tools for data handling and management.
  • SAP HANA Appliance: It is the Vendor hardware in which we install SAP HANA software.
  • SAP HANA Application Cloud: It is the cloud-based infrastructure ensuring the functioning of appliances.

15) Which platforms SAP HANA supports?


SAP HANA supports various platforms:

  • Microsoft Windows Vista, 7, 8, Server 2008 (32-bit)
  • Microsoft Windows 7, 8, 10, Server 2008 / R2 (64-bit)
  • SUSE Linux Enterprise Server (SLES) 11 (64-bit)
  • Red Hat Enterprise Linux (RHEL) 6 (64-bit)
  • Mac OS X Mavericks (10.9)

16) What do you understand from in-memory computing? What is its significance in SAP HANA?


In the in-memory computing, a huge amount of data as the information is stored in the Random-Access Memory (RAM) instead of external storage disks. This technology replaces the traditional way of storing data in disks and uses relational database management methods to fetch and process the data. In-memory computing technology is much cheaper and faster than the traditional database system.

Applications in SAP HANA are developed in close association with the database and there is close to no data movement involved from the database to the system. SAP HANA keeps a primary copy of the data ready in in-memory storage which results in data access and processing for ad-hoc reporting, analysis of data in real-time, and quick query response. Also, it reduces data complexity, data redundancy, data footprint, hardware and IT costs.

17) What are the main components of the SAP HANA environment?


The primary components of the SAP HANA environment are:

In-memory computing engine: This is a component residing within the Index Server. It has got several sub-components such as Planning Engine, Session Management, Disk Storage, Request Processing and Execution Control, Relational Engine, etc.

Database: This has raw data residing in the ERP database which is sent to the HANA database. Replication Agent (in ERP DB) and Replication Server (in the computing engine) provisions this data movement. This component provides log-based data provisioning.

SAP Business Objects BI 4: This component includes tools like SBO BI Information Designer tool, Data Services Designer, Data Services Server, and Data servers, etc. We use the components for job-based data provisioning. They design and implement a job on data and store the reports created in the form of a result. Therefore, it also acts as a repository.

SAP HANA Studio: This is a user interfacing platform which an Eclipse-based tool where we can manage, administer and manipulate data. We can work on several views like Attribute, Analytic, and Calculation.

Clients: These are miscellaneous reporting tools which we can connect to the computing engine by utilizing specific drivers. We can design and share reports by utilizing these tools and client applications.

18) What is the function of a Replication server?


The replication server is responsible for managing the replication of table data as well as metadata from the data source.

19) What is a persistence layer?


The persistence layer is mainly responsible for processing data backups periodically and storing it permanently. This is known as “Savepoints” and by default, the savepoint frequency is in every 5 minutes. The data stores as log volumes and data volumes.

20) What are the architectural components of SAP HANA?


The SAP HANA system consists of different components which together makes its system architecture.

Index server: The Index Server is the main server in SAP HANA. It has the data storage and processing engine. Queries in different languages like SQL and MDX are received in the index server. Then, the queries are processed by different components and servers within it. Index server also manages the transactions and authentications. It also has a component that manages transaction logs and selectively stores data.

In addition, the index server is further divided into smaller components like relational data engine, session manager, authorization management, planning engine, calc engine, and persistence layer.

Name server: Name server maintains the information of the topology or landscape of SAP HANA system environment. It contains information related to the name and location of the HANA components. This server manages and monitors the topology of all the distributed servers or nodes. It increases the processing time by decreasing the re-indexing process as it keeps the information on what data stores in which server.

Pre-processor server: Pre-processor server is a text analyzing server which processes textual data. The service provided by this component is used during text search. Whenever a request initiates, this server processes textual data and provides it to the user.

SAP HANA Studio Repository: The repository stores information related to the newly released updates. We can update the old version to the latest ones with the help of this.

XS Engine: It facilitates communication between the external applications (Java and HTML based) and SAP HANA system via HTTP/HTTPS in a web browser. The XS Engine converts the system’s state from the persistence model stored in the database into the consumption model for clients.

    Subscribe For Free Demo

    21) What is the most important component in SAP HANA architecture?


    The Index Server is the most important component of SAP HANA architecture. It has the data storage (having the actual data) component and a processing engine. Queries in different languages like SQL and MDX are received in the index server. These queries are processed by different components and servers within the index server.

    22) Name the components of an index server.


    There are six main components of an index server:

    • Relational data engine
    • Connection and Session manager
    • Authorization manager
    • Planning engine
    • Calc engine
    • Persistence layer

    23) What is sizing in SAP HANA?


    Sizing in SAP HANA refers to determining the hardware requirements for specific SAP HANA installation requirements. Hardware components important for sizing point of view are CPU, memory (RAM) and hard disk. The most crucial task in sizing is to estimate the size of the server best suited for the business user’s requirements.

    In SAP HANA, we can perform sizing in three ways:

    • Using Quick Sizer tool
    • Using DB script
    • Using ABAP report

    24) What are row and column storage in SAP HANA?


    Data in the SAP HANA database stores in two ways;

    • Row storage

    • Column storage.

    Row storage is the method of storing data in a horizontal fashion. It is similar to how data is stored traditionally in disk databases. However, there is one main difference between the SAP HANA row storage and traditional row storage. That is, in SAP HANA, data is stored in rows in the main memory and in traditional databases, data is stored in rows in the disk storage.

    Column storage method stores data in a columnar fashion (linear/ vertical). Data is compressed efficiently in column stores. It improves SAP HANA’s performance by optimizing both the read and write operations on data. Data is stored in the column storage area which is divided into two sections; Main storage and Delta Storage.

    25) What are the different perspectives in SAP HANA Studio?


    The SAP HANA Studio contains different perspectives which we can choose to work on. Some commonly used perspectives are:

    • SAP HANA Administration Console
    • SAP HANA Modeler
    • Application Development
    • Lifecycle Management
    • SAP HANA Development
    • ABAP
    • BW Modeling

    26) What is SAP HANA System Monitor?


    Using the system monitor in SAP HANA Studio, we can administer and monitor the system’s health and availability of SAP HANA components. Also, using the system monitor, we can access the system’s details and configurations and the services offered by different SAP HANA components.

    We can monitor several aspects through the SAP HANA system monitor such as the alerts, disk space, log disks, trace disk, data disk, memory, performance, volume, etc. Thus, it is convenient to manage individual aspects, tasks, and components.

    27) What all administrative operations can we achieve from the Administration Console?


    A number of administrative tasks can be performed in the SAP HANA Studio such as; regulating (start/stop) services, monitoring the system, audit policy, and security configuration, user management and authorization, backup and recovery, memory management, license management, alerts and messages, etc.

    All of these tasks can be performed from different tabs present in the administration console of SAP HANA Studio such as:

    • Overview (monitor and general management)
    • Alerts (position and view the details of the alerts)
    • Performance (evaluates the performance of the system for the activities happening in the database)
    • System Information (access system information files and queries)
    • Landscape (check of all running services)
    • Volumes (details of the logs and data volumes)
    • Trace Configuration (includes the traces set up information)
    • Configuration (includes the information on system configuration files)
    • Diagnosis Files (includes the system log files)

    28) What is SAP HANA Information Modeler?


    Information Modeler lets us design information views or models on top of SAP HANA database using tables in it. Such models are created to serve a business logic and operation. They are generated directly on top of the HANA database layer. The information modeler provides the interface and tools to select attributes and measures from the database tables so that the user can create multiple information views using the physical tables of transactional data stored in the databases. The information views are a logical representation of the data which can be further published or consumed for analytical purposes. Information modeling implements on the SAP HANA Modeler perspective of SAP HANA Studio.

    29) What is the difference between Information Modeler and Information Composer?


    The two differ from each other based on target users. SAP HANA Information Modeler is for technical users with extensive data modeling requirements and technical knowledge. They can perform a range of advanced operations related to modeling such as creating attribute views, analytic views, calculation views, processing models, data management and administration, data loading and import/export tables.

    Whereas, information composer is made for non-technical users who are not IT and data science experts (with no database or modeling knowledge). The information composer is so designed that it aids non-technical users with user-friendly interface, animations, hints, and suggestions for modeling and reporting.

    30) What are the three types of information views?


    The three types of information views are:

    • Attribute view

    Attribute view uses attributes, or the non-measurable, non-quantifiable data to design views and models according to the business logic. Thus, the data used in attribute view is referred to as ‘Master data’ as it is used as reference information in other views (analytic and calculation). The tables in attribute view do not contain any facts or measure.

    • Analytic view

    In an analytic view, we can create star schemas, having a central transaction or fact table and multiple dimension tables linked to it via primary keys. The measures are contained only in the central transaction table which can be grouped or joined with multiple dimension tables.

    • Calculation view

    Calculation view is an advanced model which uses both attribute and analytic view elements in it to make a complex data model following complex business logic.

    It gives us the freedom to combine and create from a range of options like tables, column views, analytic views, attribute view, etc. It enables us to do multidimensional reporting using measures and dimensions from different sources.

    Course Curriculum

    Enroll in SAP HANA Certification Course & Get Hired By TOP MNCs

    Weekday / Weekend BatchesSee Batch Details

    31) What are the types of SAP HANA engines?


    There are three types of SAP HANA engines:

    • Join Engine: We use the join engine every time an attribute view is created or used, or a join condition is applied in a native SQL command.
    • OLAP Engine: We use the OLAP engine in the creation of analytic views. We use it only when attributes are used in the analytical view and no calculation is done. If operations like calculations, counters, restricted measures are used then other engines like a calculation engine is used along with the OLAP engine.
    • Calculation Engine: We use the calculation engine in calculation along with being used in other views like analytical and attribute view whenever they apply complex logic and calculation operations.

    32) Explain How Sql Statement Is Processed?


    In the HANA database, each SQL statement is implemented in the reference of the transaction. New session is allotted to a new transaction.

    33) How To Perform Backup And Recovery Operations?


    During a regular operation, data is by default stored to the disk at savepoints in SAPHANA. As soon a there is any update and transaction, logs become active and get saved from the disk memory. In case of power failure, the database restarts like any other DB returning to the last savepoint log state. SAP HANA requires backup to protect against disk failure and reset DB to the previous state. The backups simultaneously as the users keep performing their tasks.

    34) Define Slt Configuration?


    Configuration is the meaningful information to establish a connection between source, SLT system and SAP HANA architecture as stated in the SLT system. Programmers are allowed to illustrate a new Configuration in Configuration and Monitoring Dashboard.

    35) What Is Stall?


    The waiting process for data to load from the main memory to the CPU cache is called Stall.

    36) List The Merits And Demerits Of Using Row-based Tables.?



    • No data approach can be faster than row-based if you want to analyze, process and retrieve one record at one time.
    • Row-based tables are useful when there is specific demand of accessing complete record.
    • It is preferred when the table consists of less number of rows.
    • This data storage and processing approach is easier and effective without any aggregations and fast searching.Demerits:
    • The data retrieval and processing operations involve the complete row, even though all the information is not useful.

    37) What Is The Main Sap Hana Database Component?


    Index Server consists of actual data engines for data processing including input SQL and MDX statements and performs authentic transactions.

    38) Explain The Concept Of Persistence Layer.?


    The persistence layer in SAP HANA handles all logging operations and transactions for secured backup and data restoring. This layer manages data stored in both rows and columns and provides steady savepoints. Built on the concept of persistence layer of SAP’s relational database, it ensures successful data restores.
    Besides managing log data on the disk, HANA’s persistence layer allows read and write data operations via all storage interfaces.

    39) Explain What Is Schema Mapping In Sap Hana ?


    Schema mapping is done when the physical schema in the target system is not the same as the physical schema in the source system. As mentioned earlier, suppose we are moving components from Development System (DEV) to Production System (PROD).

    The tables in DEV reside in DEV_SCHEMA and the same tables reside in PROD system in PROD_SCHEMA schema. If an attribute view is transported from DEV to PROD, it will not work because the schema name is referenced in the definition of attribute view. In order for the promoted objects to work in PROD, schema mapping needs to be set up in the target system.

    40) What Are System Requirements For Sap Hana?


    Java JRE 1.6 or 1.7 must be installed to run the SAP HANA studio. The Java runtime must be specified in the PATH variable. Make sure to choose the correct Java variant for installation of SAP HANA studio:

    32-bit installation, choose a 32-bit Java variant.

    For a 64-bit installation, choose a 64-bit Java variant.

    41) What Is A Delivery Unit In Sap Hana?


    Delivery unit (DU) is a container used by the Life Cycle Manager (LCM) to transport repository objects between the SAP HANA systems.

    The name of Delivery Unit must contain only capital letters (A-Z), digits (0-9) and underscores (_).

    42) Why To Configure Import Server In Sap Hana ?


    In order to load data from external sources to SAP HANA we need to establish a connection with the server. To connect, we need to provide details of Business Objects Data Services repository and ODBC drivers. Once the connection is established, we can import the tables definition and then load data into table definition.

    43) Explain The Column And Row Store In Hana?


    • HANA supports both type of data store in database.
    • Row store is used when you need to use Select statement and no aggregations are performed.
    • Column store is used to perform aggregations and HANA Modeling is supported only on Column based tables.

    44) What Are The Different License Keys Types In Hana System? What Is Their Validity?


    • Temporary License key
    • Permanent License Key

    Temporary License key:

    • Temporary License keys are automatically installed when you install the HANA database.
    • These keys are valid only for 90 days and you should request permanent license keys from SAP market place before expiry of this 90 days period after installation.

    Permanent License Key:

    • Permanent License keys are valid till the predefine expiration date.
    • License keys specify amount of memory licensed to target HANA installation.

    45) What Is The Difference Between Catalog And Content Tab?


    Catalog: This contains RDBMS objects like schemas, tables, views, procedures, etc.

    you can open SQL editor and design database objects.

    Content tab: This is used to maintain design time repository. You can create new packages and design Information views in HANA system. Various views can be created under content tab to meet business requirement and to perform analytical reports on the top of the Modeling views.

    46) What Are The Advantages Of Attribute View?


    • Attribute View act as Master data context, which provides Text or Description for Key/Non-key field.
    • Attribute View can be reuse in Analytic View and Calculation View.
    • Attributes View is used to select a subset of columns and rows from a database table.
    • Attributes (fields) can be calculated from multiple table fields.
    • There is no measure and aggregation option.

    47) Which Engine Is Used To Create Attribute View?


    • Join engine is used to create attribute view
    • This engine is used when we execute any Attribute View in HANA or run native SQL on more than one table with join condition.
    • If there are any calculations involved either in Attribute View or in native SQL then Join Engine will use Calculation Engine for calculations or fetch the result.

    48) What Are The Different Types Of Nodes In Calculation View?


    Different types of nodes, they are:

    Join: This node is used to join two source objects and pass the result to the next node. The join types can be inner, left outer, right outer and text join.Note: We can only add two source objects to a join node.

    Union: This is used to perform union all operation between multiple sources. The source can be n number of objects.

    Projection: This is used to select columns, filter the data and create additional columns before we use it in next nodes like a union, aggregation and rank.

    Aggregation: This is used to perform aggregation on specific columns based on the selected attributes.

    Rank: This is the exact replacement for RANK function in SQL. We can define the partition and order by clause based on the requirement.

    49) What Is Calculation View With Star Join?


    Calculation View with Star Join :

    • It does not allow base column tables, Attribute Views or Analytic views to add at data foundation.
    • All Dimension tables must be changed to Dimension Calculation views to use in Star Join.
    • All Fact tables can be added and can use default nodes in Calculation View.

    50) Which Engine Is Used To Create Analytic View?


    • This engine will be called in the backend whenever we run any queries on Analytic Views in SAP HANA.
    • If there are no additional calculations performed like calculated columns, restricted measures and counters, then everything will be processed in OLAP Engine.
    • OLAP Engine acts as join engine for those Attribute Views used in Analytic Views, without any calculated columns
    • All the join engine work will be converted into ‘BwPopJoin’ which is part of OLAP Engine.
    • If there are any calculations present, to be performed then Calculation engine will be used along with OLAP Engine.
    Course Curriculum

    Best SAP HANA Training By TOP-Rated Database Instructors

    • Instructor-led Sessions
    • Real-life Case Studies
    • Assignments
    Explore Curriculum

    51) Tell Something You Know About Normalization And De-normalization?


    Normalization is nothing but the process that is adopted for the purpose or removing the redundant data from the database. This is generally done by splitting the table into different sections. This actually makes sure of integrity. On the other side, the de-normalization is the process of considering the redundant data so that all the queries which are complex can be enhanced in terms of overall performance. 

    52) What Sort Of Advantages Do Businesses Have With Effective Database Management?


    • By data managing the users are free to derive results that can be considered for the long run
    • A lot of difficulties related to data can be avoided easily
    • The data can be managed in sections and can be accessed easily
    • Well managed data is useful in designing reports, preparing documents and assisting various departments in other tasks.

    53)  What Exactly Is The Significance Of Persistence Layer In Sap Hana?


    It is actually an important later in SAP HANA which plays a very important role. Actually, HANA has a computing engine built inside and the users have to utilize the data directly without taking any backup. The same can create an issue during powerful failure and thus it is necessary to keep a backup of the same. This layer comes as a savior and it make sure no loss of data during such a situation.

    54) What Are The Benefits That Sql Can Bring For You?


    If the queries in the SQL are simple, the users are free to retrieve a very large sum of data very easily from the system. Another good thing about SQL is it is very easy to learn and implement. There is a vast support available for SQL and all the queries can be addressed reliably. Using SQL, the database can be managed very easily and in fact without considering a large amount of coding

    55) What Is The Best Way To Manage, Operate, And Monitor Sap Hana Systems?


    Sap Hana is a young database with interesting features of SAP HANA. First of all Sap Hana is an in-memory database. It is accessible for administration via various channels. Directly from the Server, It is not the most convenient method but you can use hdbsql to manage databases. With the web-based interface Hana cockpit, you can browse and manage sap hana environments. The Client Hana Studio is the complete tool to administer Sap Hana but it has to be physically installed and therefore is dependent on the client hardware.

    56) How To Secure A Sap Hana User Connexion?


    A Sap Hana database user is protected in the first place with a password. However, a password is very often required at the command line in order to connect and execute a batch or an SQL script. The username and password are then visible to anyone. In order to avoid that situation, it is possible to create a special key in relation to a particular user. Username and password are then invisible via the use of that key.

    57) Compare SAP HANA and BWA (Business Warehouse Accelerator). Also, state how is SAP HANA working currently ?


    BWA or (Business Warehouse Accelerator): BWA is known as an in-memory accelerator for Business Warehouse (BW). The main focus of BWA is on improving the query performance of SAP Net Weaver BW. BWA is particularly designed to accelerate BW queries and also for reducing the data acquisition time by persisting the copies of the info cube.

    SAP HANA: SAP HANA is an in-memory database. It is a platform where high-performance analytic reports and application is found. Another thing to notice here is that in SAP HANA data can be loaded from SAP and non-SAP Source System through SLT, BODS, DXC, and Sybase. This can be viewed using SAP BO/BI, Crystal Reports or Excel.

    Currently, SAP HANA is working as an in-memory database for SAP BW. And now SAP HANA is able to improve the overall performance of SAP Net weaver BW.

    58) What are the types of Relational Data stored in HANA?


    There are two types of relational data stored in HANA. They are:

    • Row Store
    • Column Store

    59) Mention the different compression techniques in SAP HANA?


    There are three different compression techniques in SAP HANA and they are:

    • Run-length encoding.
    • Cluster encoding.
    • Dictionary encoding.

    60) What do you mean by latency?


    Latency is the length of time required to replicate data from the original system to the new system i.e. from the source system to the targeted system.

    70) What happens when the replication is suspended for a long period of SLT or HANA system?

    Ans :When the replication is suspended for a longer period of time of SLT or HANA system then the actual size of the logging tables increases.

    61) Explain how the SQL statement is processed?


    In the HANA database, each SQL statement is basically implemented in the reference of the transaction. Therefore in the further process, the new session is allotted to a new transaction.

    62) What is the reason for going In-memory?


    One reason is the number of CPU cycles per second is increasing and the cost of processors is decreasing. For managing the data in memory, there is five-minute rule which is based on the suggestion that it costs more to wait for the data to be fetched from disk than it costs to keep data in memory so it depends on how often you fetch the data.

    For example there is a table and no matter how large it is and this table is touched by a query at least once every 55 minutes, it is less expensive (in hardware costs) to keep it in memory than to read it from memory and if it is frequently accessed it is less expensive to store it in memory.

    63) What is a Five-minute rule?


    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 cache are re-used every 5 minutes”.

    64) Is it possible to join tables of row-based with column-based tables?



    65) Are column-based tables always the better choice than row-based tables?


    No. There are also situations in which row based tables are advantageous.

    66) Why materialized aggregates are not required?


    With a scanning speed of several gigabytes per millisecond, in-memory column stores, make it possible to calculate aggregates on large amounts of data on the fly with high performance. This is expected to eliminate the need for materialized aggregates in many cases.

    67) What are the advantages of Eliminating materialized aggregates?


    No additional tables for storing aggregate results means:

    Simplified data model

    Simplified application logic

    Higher level of concurrency and

    With the fly Aggregation we have aggregated values up to date

    68) What is parallelization?


    Column-based storage makes it easy to execute operations in parallel using multiple processor cores. In a column store data is already vertically partitioned means that operations on different columns can easily be processed in parallel. If multiple columns need to be searched or aggregated, each of these operations can be assigned to a different processor core. In addition operations on one column can be parallelized by partitioning the column into multiple sections that can be processed by different processor cores (core 3 and 4 below).

    69) Is it possible to load and replicate data from one source system to multiple target database schemas of HANA system?


    Yes. It is possible for up to 4.

    70) Is it possible to specify the type of data load and replication?


    Yes either in real time, or scheduled by time or by interval.

    SAP Hana Sample Resumes! Download & Edit, Get Noticed by Top Employers! Download

    71) What happens when you set-up a new configuration?


    The database connection is automatically created along with GUID and Mass transfer id (MT_ID).

    A schema GUID ensures that configurations with the same schema name can be created.

    The Mass transfer ID is used in the naming of SLT jobs and the system can uniquely identify a schema.

    72) What factors influence the change/increase the number of jobs?


    Number of configurations managed by the SLT replication server

    Number of tables to be loaded/replicated for each configuration

    Expected speed of initial load

    Expected replication latency time.  As a rule of thumb, one BDG job should be used for each 10 tables in replication to achieve acceptable latency times.

    73) If you set the parameter “data transfer jobs” to 04 in a configuration “SCHEMA1”, a mass transfer ID 001 is assigned. Then what jobs should be in the system?


    1 Master job (IUUC_MONITOR_SCHEMA1)

    1 Master Controller job (IUUC_REPL_CNTR_001_0001)

    At most 4 parallel jobs for MT_ID 001 (DTL_MT_DATA_LOAD_001_ 01/~02/~03/~04)

    Performance:  If lots of tables are selected for load / replication at the same time, it may happen that there are not enough background jobs available to start the load procedure for all tables immediately. In this case you can increase the number of initial load jobs, otherwise tables will be handled sequentially.

    For tables with large volume of data, you can use the transaction “Advanced Replication Settings (IUUC_REPL_CONT)” to further optimize the load and replication procedure for dedicated tables.

    74) What are the different replication scenarios?


    Load, Replicate, Stop, Suspend and Resume.

    Before you select any application table, the initial load of the tables DD02L, DD02T & DD08L must be completed as they contain the metadata information.

    Load: Starts an initial load of replication data from the source system. The procedure is a one-time event. After it is completed, further changes to the source system database will not be replicated.

    For the initial load procedure, neither database triggers nor logging tables are created in the source system. Default settings use reading type 3 (DB_SETGET) with up to 3 background jobs in parallel to load tables in parallel or subsequently into the HANA system.

    Replicate: Combines an initial load procedure and the subsequent replication procedure (real time or scheduled).

    Before the initial load procedure will start, database trigger and related logging table are created for each table in the source system as well as in SLT replication server.

    Stop Replication: Stops any current load or replication process of a table.

    The stop function will remove the database trigger and related logging tables completely. Only use this function if you do want to continue a selected table otherwise you must initially load the table again to ensure data consistency.

    Suspend: Pauses a table from a running replication. The database trigger will not be deleted from the source system. The recording of changes will continue and related information is stored in the related logging tables in the source system.

    If you suspend tables for a long time the size of logging tables may increase and adjust the table space if required.

    Resume: Restarts the application for a suspended table. The previous suspended replication will be resumed (no new initial load required).

    75) What happens if the replication is suspended for a long period of time or system outage of SLT or HANA system?


    The size of the logging tables increases.

    76) Maximum number of tables in a schema?



    77) What can be the maximum table name length?


    127 characters

    78) What can be the maximum column name length?


    127 characters

    79) What can be the maximum number of columns in a table?



    80) What can be the maximum number of columns in a view?



    81) What can be the maximum number of partitions of a column table?



    82) What can be the maximum number of rows  in each table?


    Limited by storage size RS: 1TB/sizeof(row)

    CS: 2^31 * number of partitions

    83) In which table you can get the current system limits?



    84) Maximum number of jobs you can view the information in the Current tab of Job log?



    85) What happens when you compile the procedure?


    During compilation, the call to the procedure is rewritten for processing by the calculation engine.

    86) What happens when you execute the procedure?


    It binds the actual parameters to the calculation models generated in the definition phase.

    87) What is CE plan operator? What are the different categories?


    CE plan operator does the data transformation functionality internally and used in definition of functions. It is an alternate to using SQL statements.

    Data Source Access operators that bind a column table or a column view to a table variable. (CE_COLUMN_TABLE, CE_JOIN_VIEW, CE_OLAP_VIEW, CE_CALC_VIEW)

    Relational operators that allow a user to bypass the SQL processor during evaluation and directly executed in the calculation engine.


    Special extensions implement, e.g., crucial business functions inside the database kernel.


    88) What is  CE_OLAP_VIEW operator?


    It return results for an existing OLAP view (also known as Analytical view). It takes the name of OLAP view and an optional list of key figures and dimensions as parameters. The OLAP view is grouped by dimensions and the key figures are aggregated using the default aggregation of the OLAP view.


    • out = CE_OLAP_VIEW (“OLAP_view”,[“Dim1”, “kf”]);

    Is equivalent to

    • out = SELECT dim1, SUM(kf) FROM OLAP_view GROUP BY dim1;

    89) What is Repository?


    The HANA Repository is storage system for development objects and is built into SAP HANA.

    The repository supports Version control, Transport, and Sharing of objects between multiple developers. We can add objects to the repository, update the objects, publish the objects, and compile these objects into runtime objects.

    90) What is an Attribute?


    Attribute represents the descriptive data used in modeling. Example: City, Country, etc.

    Are you looking training with Right Jobs?

    Contact Us
    Get Training Quote for Free