➢ High Performance ANalytical Appliance

➢ Transaction Processing (OLTP)

➢ Day to Day transactions will be stored in OLTP systems

➢ No intelligent analysis will be done

➢ Analytical Processing (OLAP)

➢ Data will be pulled from OLTP

➢ Intelligent analysis and Reporting will be done

➢ HANA-HAsso Plattner New Architecture. It is not acronym, name of Hasso Plattner(One of SAP
Founder)

➢ HANA-High performance ANalytical Appliance (technical name)

SAP AG developed following appliances

1) Live cache (used in SAP APO, Advanced Planner and Optimizer)

2) BWA/BIA (Business Warehouse Accelerator used in B.W for performance)

3) SAP HANA.

➢ Appliance is merger of s/w and h/w. After founder name HANA is technically called as High
performance Analytical appliances

➢ OLTP Vs OLAP

➢ Writing is important in OLTP Vs Reading is important in OLAP

➢ After fine tuning using all the best possible methods, the DB performance cannot be
improved after certain extent.

➢ Traditional Databases

➢ Oracle/MS SQL/TeraData/IBM DB2/Sybase IQ

➢ BW – Business Warehouse

➢ Data from OLTP systems will be pulled into BW using various methods.

➢ Data will be parsed into multiple info providers

(Infoobject/DSO/Infocube/Multiproviders)

➢ Reporting will be done using this info providers (BPC/BOBI/BEX)

▶ BWA – Business Warehouse Accelerator

▶ In memory computing
 ▶ When the data is pushed to DB, a separate algorithm triggers and stores data into BWA

▶ Disadvantages: During power outage, by that time BWA boots up, the queries use DBs
to process reports and analysis

▶ During a first run of a query, it takes same time as of running in DB. Second run will give
results faster.

▶ The records stored in BWA are duplicate of DB. Maintenance and Cost additional.

▶ Data reading performance improved using in memory computing method

▶ Data loading performance also improved

▶ Reading performance was improved as it was processed from RAM

▶ Example:

A recent analysis showed that a complex query on customer sales information (460 billion
records – 50 TB storage) retrieved from traditional database took 77 minutes. Whereas using HANA, it
took stunning 17 seconds to fetch the results

▶ A specially made processors combined to form a HANA server***

▶ One processor with 12 cores

▶ 1 layer with 8 processors (Intel XEON CPUs) = 96 cores

▶ 4 such layers then combined to form a single server which can perform 384 operations
at any point of time

▶ This enables MPP (Massive Parallel processing)

▶ Special attention was given while designing the in memory computing engine.

▶ Data stored in In-Memory (Main Memory) will not be erased during power outage with
the efficient backup process.

▶ For this they have used Page Management and Logger to form a persistent layer

▶ Both will be storing data in the physical mechanical device with partition for Data
volumes and Log volumes.

▶ TREX search engine

▶ Text Retrieval and Extraction - Search algorithm was written effectively

▶ Sybase IQ

▶ Column Storage of data

▶ P*Time Database - Transit in Memory

▶ This brings the capability of row storage. It thinks in TREX format and stores
data faster than any other traditional DB. Loading is faster than Retrieving.
 ▶ Persistent Layer - MaxDB

▶ Data will be pushed from In-memory (Persistent Layer) to Mechanical Device.

MaxDB provides this to happen seamlessly

Majority of the time taken (60%) is to retrieve the data from database and put it in application server.

In application server the logic is written to massage the data and prepare it for output.

The output which is normally a report/extract will then be displayed.

HANA, instead massages and prepares the data in DB itself using stored procedures. Thus reducing the
time taken for data shuttling between DB and AppServer.
Information composer and Modeling studio

Application services

Text search using TREX engine

Planning and calculation engine

Predictive Analysis & BFL

R & Hadoop Integration – R (River Language) used for statistical computing

Real time replication services using SDA

In-Memory Database

Data Services

▶ HANA as a Database

▶ HANA as a Data Mart

▶ HANA as a Accelerator

▶ Mixed – Database and Data Mart

 ▶ HANA on cloud

▶ HANA – Development of new apps in XS engine

All the data from SAP and NON SAP systems can use HANA as its database.

Various techniques are used to bring data into HANA (BODS/SLT/DX/SDA/Flat files)

HANA has a provision to integrate Hadoop (Big Data) into its database.

In future HANA will be a standalone database which supports all SAP and Non SAP applications
Row storage Vs Column Storage

While writing, it writes the data in a row storage format

While reading, it retrieves the data from a column storage tables

Now when you write the data 5 minutes before and you want to read it, the algorithm will read the data
from both column storage and row storage from the RAM and displays the data.

▶ Once data is brought using various techniques (BODS/SLT/SDA/DX/Flat files), we can build
models on top of this columnar tables.

▶ SAP HANA studio will be used for this purpose

▶ Attribute view/Analytical view/Calculation view will be created.

▶ Using Analytical and Calculation view report can be generated using SAP BO/BEX

▶ Tailpiece

▶ This does not mean BW will be phased out. Since BW models are prepared already by
client, bringing entire models into HANA will take lot of time.

▶ Only for particular application performance improvement, HANA can be used as a secondary
database.
 ▶ As Attribute view/Analytical view/Calculation view will be created using columnar tables, which
stores the data in effective way, thus increasing the performance. Hence BWA is not required

▶ Speed, you will see the tremendous increase in speed of the report being generated

▶ No data duplicates and additional maintenance cost involved.

As HANA will be acting as Database. We can build models using HANA studio on top of this.

BW can be plugged into HANA and use it as a Database. Still we can use BW models and do reporting
using BW reporting tools.

▶ To operate on cloud, HANA is possessing required license.

▶ Client will decide on the size of disk space and RAM requirements.

▶ Then as per the calculation 1/4th space of requested disk space and equal size of RAM will be
allotted.

▶ HANA performs the same as on-premise and cloud. However the speed is determined based on
the network speed.

▶ HANA is a platform with a powerful XS engine.

▶ Any application compatible with HANA can be implemented (SAP Lumira)

▶ Additional applications can be built on top of XS engine and can be incorporated into business
(Example – Bid Processing – Between purchase order and sales order).

▶ This responds to any http/https requests

▶ Develop any application using front end tool SAP UI5 (HTML5 + CSS + JS + Lib) and Services
OData Services (JAVA Scripting + XMLA + SQL scripting) is called native development
▶ ABAP + JAVA + .Net + C/C++ called non native development

▶ R (River Language) Language can also be used for statistical computing.

▶ HANA Administration – DBA + SUSE Linux + Cloud security

▶ HANA - Front end developers - SAP Fiori will be the front end

▶ SAP UI5(HTML5+CSS+JS+Libraries)+OData services + Java scripting + XML + SQL Scripting

▶ Programming languages to be used ABAP + Java + DotNet + C/C++

▶ HANA is a combination of Software + Hardware

▶ HANA can be implemented on-premise or on cloud

▶ XS engine provides a gateway for building small applications on top of your regular SAP/NonSAP
applications

▶ HANA can operate as a Database/Data Mart/Mixed

▶ XS engine Exchange application server SP5

▶ ODTA read till SP5

▶ If BW is there HANA?

▶ BW can be removed and migrate everything to HANA by creating all reporting

▶ from BW 7.3 SP5,flexibility to have HANA data base sitting on BW

▶ HANA is only database and BW is data warehouse application. BW is increased with HANA
coming and becomes hybrid.

▶ ECC is more compatible with HANA is called simple finance /simple logistics. Number of tables
go down

▶ What is the latest version of SPS and S4 HANA sits?