What Is Sap Hana?: General Questions
What Is Sap Hana?: General Questions
What Is Sap Hana?: General Questions
General Questions:
SAP HANA is one of the fastest growing products in SAP’s history and is viewed by
the industry as a break through solution for in-memory databases. SAP HANA claims
that it accelerates analytics and applications on a single, in-memory platform as well
as combining databases, data processing, and application platform capabilities.
The SAP HANA studio runs on the Eclipse platform 3.6. We can use the SAP HANA
studio on the following platforms:
• Microsoft Windows x32 and x64 versions of: Windows XP, Windows Vista,
Windows 7
• SUSE Linux Enterprise Server SLES 11: x86 64-bit version
Note: For Mac OS, HANA studio is available but there is no HANA client for that.
INTERVIEW QUESTIONS FOR “SAP HANA-DATA MODELLING”
They are all the same thing, and 1.0 SP03 is touted to be the final name which should
go into Ramp Up (beta) in Q4 2011. This allows any SAP Net Weaver BW 7.3 Data
Warehouse to be migrated into a HANA appliance. HANA 1.0 SP03 specifically also
accelerates BW calculations and planning, which means even more performance
gains can be attained.
6. What is a restricted user in SAP HANA system?
Restricted users are those users who access HANA system with some applications
and they don’t have SQL privileges on HANA system. When these users are created
they don’t have any access initially.
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.
11. 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.
Meta Data:
Meta Data is data about Data. It tells you about the structure of data or Meta
Objects.
Master Data:
This Data is key business information like Customer information, Employee,
Materials etc. This is more like a reference data. For Ex. If a customer orders 10
units of your product instead of asking customer for his shipping address 10 times
the same can be referenced from the Customer Master Data.
Transaction Data:
This is data related to day to day transactions.
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 (_).
INTERVIEW QUESTIONS FOR “SAP HANA-DATA MODELLING”
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.
We need to import the tables T006 & T006A for Unit of Measures
17. 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.
Only operating system that is supported by HANA is Suse Linux Enterprise Server
SP1/SP2 (SLES SP1/2).
19. What are the different license keys types in HANA system? What is their validity?
Permanent License keys are valid till the predefine expiration date. License keys
specify amount of memory licensed to target HANA installation.
INTERVIEW QUESTIONS FOR “SAP HANA-DATA MODELLING”
Catalog −This contains RDBMS objects like schemas, tables, views, procedures, etc.
You can open SQL editor and design database objects.
Content −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
Modeler: used for creating various types of views and analytical privileges.
SAP HANA Development: Used for programming applications for creating
development objects to access or update data models such as Server-side Java script
or HTML files.
Administration: Used to monitor the system and change settings.
Debug: Used to debug code such as SQLScript (.procedure files) or Server-side Java
script (.xsjs files).
Index Server consists of actual data engines for data processing including input SQL
and MDX statements and performs authentic transactions.
Using the columnar data storage approach, the workload in SAP HANA is divided
vertically. The columnar approach allows linear searching and aggregation of data
rather than two-dimensional data structure. If more than one column is to be
processed, each task is assigned to diverse processor. Operations on one column are
then collimated by column divisions processed by different processors.
25. Will the table size in SAP HANA database and in the source system the same?
Schema mapping is done when the physical schema in the target system is not the
same as the physical
schema in the source system.
Note: Schema mapping only applies to references from repository objects to catalog
objects. It is not intended to be used for repository to repository references.
A Join clause combines records from two or more tables /view in a database.
SAP HANA supports following types of join.
1. Inner Join
2. Left Outer Join
3. Right Outer Join
4. Full Outer Join
5. Referential Join
6. Text Join
1. The INNER JOIN selects the set of records that match in both the Tables.
Where to use:
Inner join should be used if referential integrity is ensured.
Inner Join is much faster that Outer Join thus is the preferred solution if
possible from semantically perspective
INTERVIEW QUESTIONS FOR “SAP HANA-DATA MODELLING”
Attribute View: Inner Joins can be used to join different master data
tables to a joint dimension
2. The Left Outer Join selects the complete set of records from first table
(CUSTOMER), with the matching records (where available) in second
table (SALES_ORDER). If there is no match, the right side will contain
null.
3. The Right Outer Join selects the complete set of records from second table
(SALES_ORDER), with the matching records (where available) in first
table (CUSTOMER). If there is no match, the left side will contain null.
4. The FULL OUTER JOIN keyword selects all rows from the left table
(table1) and from the right table (table2).
The FULL OUTER JOIN keyword combines the result of both LEFT OUTER
and RIGHT OUTER joins.
Analytic Privileges restrict the user to view data for which they authorize. SAP
HANA Analytic Privileges is used for Security purpose.
2. What is an Attribute?
Attribute represents the descriptive data used in modeling. Example: City, Country,
etc.
Semantics
Data foundation
Column
View Properties
Hierchery
3. Semantics (Scenario Pane): This node represents output structure of the view.
Here it is Dimension.
4. Data Foundation (Scenario Pane): This node represents the table that we use for
defining attribute view.
5. Here we drop table for creating attribute view.
6. Tab (columns, view Properties, Hierarchies) for details pane will be displayed.
7. Local: Here all Local attribute detail will be displayed.
8. Show: Filter for Local Attribute.
6. 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.
INTERVIEW QUESTIONS FOR “SAP HANA-DATA MODELLING”
SAP HANA Analytic view measure can be selected from only one fact table. When
there is need of More Fact table in information view then calculation view come in
the picture. Calculation view supports complex calculation.
The data foundation of the calculation view can include tables, column views,
analytic views and calculation views.
SAP HANA Graphical Calculation View (Created by SAP HANA Studio Graphical
editor).
SAP HANA Script-based calculations Views (Created by SQL Scripts by SAP HANA
Studio).
INTERVIEW QUESTIONS FOR “SAP HANA-DATA MODELLING”
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.
Rank: This is the exact replacement for RANK function in SQL. We can define
the partition and order by clause based on the requirement.
6. What are the benefits of using Calculation view with Star join?
It simplifies the design process as allows you to select multiple measures from
multiple fact tables. Can implement 3NF using Star Join.
7. Can we call an analytic view or calculation view inside another calculation view in
SAP HANA ?
Yes. We can call all the views (attribute, analytic and calculation view) inside a
calculation view.
Note: Calculation views are composite views and can be used to combine other
views. It can consume other Analytical, Attribute, other Calculation Views & tables.
It can perform complex calculations not possible with other views.
SQL Engine:
SQL Engine which is also known as SQL Parser/interface is used for all sorts
of SQL statements generated by frontend application via different different
clients and also for native sql run at database level.
From SAP HANA SP7, we have an option for Calculation Views in ‘Properties’
section, where we have an option to choose calculation view to run in ‘SQL
Engine’. Advantage of this option is that, instead of moving data between
multiple engines HANA executes the entire script in SQL Engine to get the
final result.
Each Analytic View has one Fact table surrounded by multiple dimension
tables. Fact table contains primary key for each Dim table and measures.
Analytic Views are similar to Info Objects and Info sets of SAP BW.
INTERVIEW QUESTIONS FOR “SAP HANA-DATA MODELLING”
Create join in order to join the attributes view with the fact table.
OLAP Engine:
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.