Scribd
Upload
184 views6 pages

Sap Hana:: OLTP: Simple Queries Like INSERT, UPDATE, DELETE Etc

SAP HANA is an in-memory database that allows for real-time analysis of large volumes of data by storing the entire dataset in main memory. It overcomes issues with disk I/O that cause performance bottlenecks in traditional databases. SAP HANA utilizes massively parallel processing and a hybrid row and column storage model to improve performance. It has capabilities for both online transaction processing and online analytical processing.

Uploaded by

Sonya Reddy
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
184 views6 pages

Sap Hana:: OLTP: Simple Queries Like INSERT, UPDATE, DELETE Etc

SAP HANA is an in-memory database that allows for real-time analysis of large volumes of data by storing the entire dataset in main memory. It overcomes issues with disk I/O that cause performance bottlenecks in traditional databases. SAP HANA utilizes massively parallel processing and a hybrid row and column storage model to improve performance. It has capabilities for both online transaction processing and online analytical processing.

Uploaded by

Sonya Reddy
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

SAP HANA: SAP High-performance Analytic Appliance is an In-Memory Database from SAP to store data and analyze large

volumes of non-aggregated transactional data in real time. Meaning: Basically SAP HANA is a database. It addresses many problems which are being faced in the traditional databases through its In-Memory concept . Disk I/O- When a hard drive is used to store the data, CPU sits idle during the time the data is being written. Hence Disk I/O always causes performance bottleneck. Whereas Inmemory storage overcomes this problem since the data is stored in RAM rather than hard drive. SAP HANA utilises this technology reducing the performance risk. Hence for HANA to be installed, we need to have good hardware configuration 40 cores and 512 GB RAM. SAP HANA has both OLTP and OLAP capabilities OLTP: Simple queries like INSERT, UPDATE, DELETE etc. Returns few records Does not require much processing time OLAP: Complex aggregations sometimes combination of various OLTP queries Returns huge number of records depending upon the data Requires more processing time. EX: Data warehouses HANA Database Features: 1. In-Memory 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. Massively Parallel Processing Hybrid Database Column Store Row Store Complex Event Processing Calculation Engine Compression Virtual Views Partitioning No aggregates

1. In-Memory Feature of SAP HANA:


The basic idea to cache the entire database into Main memory so that the processor can access the data very faster and hence avoiding the Disk I/O. If the data is stored in Main memory (which is volatile), then how about data permanent persistency? SAP HANA, holds the bulk of its data in memory for maximum performance, but still uses persistence storage to provide a fall back in case of any failure. Data and log are automatically saved to disk at regular save points and the logs are saved to disk after every COMMIT of a database transaction.

Disk write operations happen asynchronously as a back ground task. Generally on system start-up, HANA loads all of its tables into memory.

2. Massively Parallel-Processing & Column Store:


Multiple CPUs are helpful in calling different algorithms in parallel and hence the performance can be easily improved. HANAs Column store feature makes it easy to execute multiple operations in parallel using multiple processor cores. Meaning: In Column Store, all the columns are vertically partitioned. This means operations on different columns can be carried out in parallel. If multiple columns need to be searched or aggregated, each of these operations will be assigned to multiples CPUs. In addition, operations on one column can be parallelized by partitioning the column into multiple sections that can be processed by different processor cores.

3. Hybrid Data Store:


Databases store data in two different ways: Row-Oriented Storage and Column-Oriented Storage. The traditional databases normally store the data in Row-Based style. What is Row-Oriented and Column-Oriented Storage? Row-Oriented Storage: Stores a table as a sequence of records each of which contains the fields of one row Column-Oriented Storage: Stores all the values of a column in contiguous memory locations. Example: EmpId 1 2 3 Lastname Smith Jones Johnson Firstname Joe Mary Cathy Salary 40000 50000 44000 Column-Oriented Storage: 1,2,3; Smith,Jones,Johnson; Joe,Mary,Cathy; 40000,50000,44000;

Row-Oriented Storage: 1,Smith,Joe,40000; 2,Jones,Mary,50000; 3,Johnson,Cathy,44000;

Row-Oriented storage is well suited for OLTP whereas Column-oriented storage is well suited for OLAP. SAP HANA is a hybrid database which contains both. And both these storages are InMemory. The HANA database allows the developer to specify whether a table is to be stored column-wise or row-wise. It is also possible to alter a table from column to row and vice-versa.

4. Higher Data Compression:

The goal of keeping all relevant data in main memory can be achieved with less cost if data compression is used. Columnar data storage allows highly efficient compression.

5. Two Processing Engines:


Well, data is in memory which is good, how do we extract a report on the data? HANA has two processing engines one is based on SQL which accepts SQL queries and the other one is based on MDX. MDX: MDX files (Multiple inDeX files) are used to hold the database information.

6. Supports Sybase Replication Server:


HANA supports Sybase replication server Sybase Replication Server can be used for real time synchronization between ERP and HANA. It is database replication software that moves and synchronizes data across the enterprise to meet a host of competing needs, including guaranteed data delivery, real-time business intelligence and zero operational downtime.

7. Modeling Studio:
HANA is connected to ERP systems - Front-end Modeling Studio can be used for load control and replication server management. Using Modeling studio we can, Specify what tables are stored in HANA Schedule data replication jobs Manage Data Services to load the data from SAP BW and other 3rd party systems Manage connections to ERP instances Use data services for their modeling Do modeling in HANA itself without depending upon data services.

8. Reporting
Client tools can access HANA directly; Like MS Excel, SAP BI Reporting tools, Dashboard tools etc can also access HANA directly Third party tools can gain advantage through the use of ODBC, JDBC and ODBO drivers in HANA HANA supports BICS interface (Business Intelligence Customer Services). BICS is used for BEx queries.

Architecture of SAP HANA:

Star Schema, Dimensional tables and Fact tables:


A fact table surrounded by its linked-in dimension tables is often called as a star schema because of the geometry of its graphical model. Fact tables are the lists of business transactions while the linked-in data are typically the master data. These linked-in data are known as dimension tables. SAP HANA Modeling Views: 1. Attribute Views 2. Analytic Views 3. Calculation Views Attribute Views: (Hits the join engine) Attribute Views are used to give master data tables context. They are used to select a subset of rows and columns from a data table. Analytic Views: (Hits the OLAP engine) Analytic views are used to build a data foundation based on transactional tables. They provide information on aggregate data such as number of cars sold per year, maximum power consumption per day etc. These views can contain two types of attributes (columns) Measure and normal attributes. Measures are the attributes for which an aggregation must be defined

If analytical views are used in SQL statements, then the measures should be aggregated using SQL aggregate functions whereas normal attributes can be handled as regular columns. Calculation Views: (Hits the calculation engine) Calculation views are defined as either graphical views or scripted views depending on how they are created. Calculation views always have atleast one measure. Calculation Engine: Used for complex calculations that cannot be carried by OLAP and Join Engine. OLAP Engine: Used for calculation and aggregation based on star schema or similar Join Engine: Used for all kinds of joins. Basic Modeling Rules To Follow: Always think in sets of data not rows of data In the case when both analytic views generate lots of records when joined, then better to go for union rather than join. A join can be used when one of the analytic views generates a less number of records (less than one million) into a calculation view. Before the data that is transferred from OLAP Engine to calculation engine, the data must be minimized this can be done using projections (by applying filter criteria). Use Set Processing for Mass Data It is very important to avoid loops while modeling since they lead to poor performance Attributes: There are three types of attributes in SAP HANA - Simple attributes, Calculated attributes and Private attributes. Simple Attributes are non-measurable analytical elements that are derived from the data. Calculated Attributes are derived from one or more existing attributes or constants Ex: Deriving a weekday name from calday. Private Attributes are used in analytic view to allow you to customize the behaviour of an attribute only for that view. If an analytic view or calculation view includes an attribute view, then it inherits the behaviour of the attributes from attribute view. On the other hand, if you create an analytic view for one specific use case in which you want a particular attribute to behave differently than how it does in the attribute view to which it belongs, you can declare it as a private attribute. Measures: Data that can be quantified and calculated (known as key figures in SAP BW). Attribute views are known as Dimensions in SAP BW.

Packages in SAP HANA: This is a procedure for grouping together the related information objects in a structured way.

You might also like