You are on page 1of 13

HA100: SAP HANA Introduction

SAP HANA (platform) flexible data source agnostic appliance. Enables analyze volumes of
SAP/Non-SAP data in real time. Avoiding need to materialize transformations
SAP HANA Appliance Software hardware/software: SAP HANA Database, SAP landscape
transportation (SAP LT), SAP HANA Direct Extractor Connection (SAP DXC), SAP data
services
SAP HANA Database in memory database row base, column base, object base database
technology, Optimized to exploit the parallel processing capabilities of modern multi-core
CPU architectures.
SAP HANA is a database. Optimize software and optimized hardware
Conventional database
Store in rows sequence of records

In Memory Database
Store in columns

For all column report - all column


relevant
Distinct value in database

Faster aggregates linear scan


Sequential memory access
Massive parallel processing possible

No aggregates
Minor number of records
Note: In the migration of SAP to SAP Hana, SAP tables are automatically migrated into the
storage type suited best. Can be viewed via SE13 or SAP HANA studio (Catalog > Open
Definition).
How SAP HANA do this?
Storage separations: (MAIN and Delta Store).
-

Enables high compressions and high write performance at the same time.
o Main Storage (Column Store - Sorted): Data compression, read optimizedfastest to be read, not for write operation
o Delta 1 ( Column Store not sorted): write optimized likely fast to be read
o Delta 2 ( Row store ): write optimized, small in size, slow to read to be
merge in the delta 1 store, short term input buffer
Delta merge operation done regularly to merge delta store to main source: Delta 2
-> delta 1 -> Main store

Software optimization
-

Classic approach process in Application layer


SAP HANA approach process in database layer (in memory platform)
SAP ABAP is upgraded to Netweaver 7.30 and 7.40
SAP ABAP focus on triggering/orchestration
Less data transfer between application and database layer
SAP HANA: Bring the logic to where data is, calculate first and then move results
SAP ABAP approach:
o Check DBMS used
o If SAP HANA, call BADI for SAP HANA
o If other DBMS, standard ABAP code

SAP HANA a spatial enabled database


- Spatial data describes position shape and orientation of objects in a defined space
- Represented as point, line, polygon and multi polygon
- ISO/IEC 13249-3 standard and open geospatial consortium (1999 SQL/ MM standard)
- There are spatial data types in SAP HANA tables (eg SHAPE, CENTERPOINT, line etc.)
- Spatial (JOIN) operations are added such as contains, crosses, intersects and
overlaps
- Spatial joins exists

3-tier Application for SAP HANA

XS services for control & queries located in the DBMS handles calculations
UI rendering in client, SAP suggests SAP UI 5 and UI integration services
UI creation, presentation, data injection should be done in client

Code push down


-

Delegating data-intensive calculation to the database layer

SAP Hana Extended Application Services Overview:


Front-End technologies: http/s, HTML5/SAPUI5, Client-side JavaScript
Control Flow Technologies: Odata, Server-Side Javascript, XMLA
Data processing technologies: SQL/SqlScript, Calculation Engine functions, Application
Function library (AFL)
SAP HANA search features
- Text Searching can search structure/unstructured text, easy creation of SAP HANA
search apps
- Analytics native text analytics, unlock text from binary documents ( 31 languages
for linguistic mark-up, 13 languages for predefined core extractions, and 5 language
for voice of the customer sentiment extraction)
- Text analysis

HA100: SAP HANA Studio


Environment for administration, modeling, development and data provisioning for SAP
HANA; java based application that runs on Eclipse platform.
Perspectives pre-defined UI layouts with several views.
Window->Open Perspective -> Other (opening a perspective)
Window-> Show View -> Other (adding view in a perspective)

SAP HANA Administration Console Perspective


SAP HANA Modeler Perspective

Views:
Systems View

System Monitor View

Content Node in System view organize per package

Nodes:
Catalog contains the tables, column views, procedures
Content contains packages (packages includes attribute vies, analytic views, procedures,
decision tables
Security Users and Roles

HA100: SAP HANA Architecture

During fail over the master server assigns the failed volume to the standby server. The
other of the 2 master volumes will be selected as active server.

HA100: SAP HANA Persistence


Data and Log Volumes
Log Volume

data is kept in memory for max performance

info about data changes (redo log)

Data volume (undo log) persistent storage


Save point every 5 minutes change data and undo log is written from memory to
persistent storage
System restart:

HA100: SAP HANA Modeler


Modeling, analytic privileges/security and DB administration

Terminologies

Modeling

Levels of modeling
Attribute views
Analytic views
Calculation views
Calculation view enhanced with analytical views

Modeling Process Flow:


1. Import Source System metadata , physical tables are
created
2. Provision data, loaded tables with content
3. Create info models, database views etc.
4. Deploy, column views are created and activated
5. Consume, SQL, BICS MDX (used)
Information Models:
1. Attribute View separate master data from fact data.
Creates attribute views
2. Analytical View create cube-like view by joining attributes
view to fact data
3. Calculation view (optional) has two types, only selects no
updates
Graphical
SQL script HANA specific function script language
- Think of SELECT FROM HANA as a data flow
- Join or union two or more data flows
4. Analytic Privileges used for row level security

You might also like