Efficient transaction processing in sap hana
-
Upload
mysa-vijay -
Category
Technology
-
view
293 -
download
1
Transcript of Efficient transaction processing in sap hana
![Page 1: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/1.jpg)
EFFICIENT TRANSACTION PROCESSING IN SAP HANA Presented by Vijay Soppadandi
21363273
![Page 2: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/2.jpg)
CONTENTS
• What is SAP HANA?
• Goal
• Agenda
• Framework
• Summary & discussion
![Page 3: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/3.jpg)
WHAT IS SAP HANA?
• High-Performance Analytic Appliance
• In-memory computing
![Page 4: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/4.jpg)
GOAL
• The overall goal of the SAP HANA database is to provide a generic but powerful system for different query scenarios, both transactional and analytical, on the same data representation within a highly scalable execution environment
![Page 5: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/5.jpg)
AGENDA
OLTP (Online Transaction Proccessing)
o large number of concurrent users and transactions
o high update load
o very selective point queries
o Row-stores
OLAP (Online Analytical Processing)
o aggregation queries over a huge volume of data
o compute statistical models from the data
oColumn-stores
![Page 6: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/6.jpg)
AGENDA
• Zoo of different systems with different capabilities for different application scenarios
• However, workloads usually contain both
o transactional database needs statistical information to make on-the-fly business decisions
o data-warehouses are required to capture transactions feeds for real-time analytics
![Page 7: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/7.jpg)
FRAMEWORK
• Layered Architecture of the SAP HANA
• Lifecycle Management of Database Records
• Types of Merging and optimization
• Summary & discussion
![Page 8: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/8.jpg)
LAYERED ARCHITECTURE OF THE SAP HANA
Reference 3
![Page 9: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/9.jpg)
FRAMEWORK
• Layered Architecture of the SAP HANA
• Lifecycle Management of Database Records
• Types of Merging and optimization
• Summary & discussion
![Page 10: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/10.jpg)
LIFECYCLE MANAGEMENT OF DATABASE RECORDS
Reference 1
![Page 11: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/11.jpg)
LIFECYCLE MANAGEMENT OF DATABASE RECORDS
• It has three main stages
- L1-delta
-L2-delta
-Main
• SAP HANA theoretically escalate records through different stages of a physical representation
![Page 12: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/12.jpg)
L1-DELTA
• Accepts all incoming data requests
• No data compressions
• Stores them in write optimized manner
- Preserves in logical-row format
-Fast insert & deleat, field update and record projections
• Holds 10,000 to 100,000 rows per single-node
![Page 13: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/13.jpg)
L2-DELTA
• The next stage of the Unified table structure
• Organized in column format
• Stores upto 10 millions of row
• It emplyoys dictionary encoding
- However, for performance reasons, the dictionary is unsorted requiring secondary index structures to optimally support point query access patterns
![Page 14: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/14.jpg)
MAIN STORE
• Represents core data
• Final data format
• Organized in column format
• Highest compression rate
-Positions in a sorted dictionary
-Stored in a bit-packet manner
-Dictionary is always comprised
![Page 15: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/15.jpg)
UNIFIED TABLE ACCESS
• A common abstract interface to access different stores •
• Records are propagated asynchronously
– without interfering with running operations
• Two transformations (or merge steps)
– L1-deta to L2-delta
– L2-delta to main
![Page 16: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/16.jpg)
L1-DETA TO L2-DELTA MERGE
• Rows format is converted into column format
- column-by-column inserted into the L2-delta
Steps for merging:
• Step 1 ( parallel)
- new entries are added (advance) to the dictionary
• Step 2 (parallel)
-using dictionary encoding technique new column values are added
• Step 3
- added values are removed from the L1-delta
![Page 17: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/17.jpg)
L2-DELTA TO MAIN MERGE
• New main structure created from L2-delta
• Resourse intensive
-Is carefully schedulled and highly optimized
• Current L2-delta is closed when its done
• Retries the merge on failure
![Page 18: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/18.jpg)
PERSISTENCE MAPPING
Reference 1
![Page 19: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/19.jpg)
CONT...
• Its fully supports ACID gurentees
• Uses REDO logs instead of UNDO mechanisms and saving point
• It has some complications in making merging process
![Page 20: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/20.jpg)
FRAMWORK
• Layered Architecture of the SAP HANA
• Lifecycle Management of Database Records
• Types of Merging and optimization
• Summary & discussion
![Page 21: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/21.jpg)
MERGE OPTIMIZATION
• Basic idea to provide transperent record propagation from write to read optimization.
• The classic merge
• Re-sorting merge
• Partial merge
![Page 22: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/22.jpg)
THE CLASSIC MERGE
• It has two phases
• In first phase generates the new sorted dictionary
• In secound phase, new main index generates on the new dictionary
![Page 23: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/23.jpg)
THE CLASSIC MERGE
Reference 1
![Page 24: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/24.jpg)
RE-SORTING MERGE
• Provides higher compression potential
• reorganizes the content of the full table to yield a data layout which provides higher compression potential
• not easy because all records should have the same order in all columns
• uses a scheme discussed in another paper
![Page 25: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/25.jpg)
PARTIAL MERGE
• It aims to reduce overall merge overhead
• Split the main into two independent main structures
- passive : Not part of the merge process
-Active : Takes part in the merge process with L2-delta
![Page 26: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/26.jpg)
PARTIAL MERGE
Reference 1
![Page 27: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/27.jpg)
CHARACTERISTICS OF RECORD STAGES
Reference 1
![Page 28: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/28.jpg)
REFERENCES
1.Efficient Transaction Processing in SAP HANA Database – The End of a Column Store Myth
-Vishal Sikka SAP 3412 Hillview Ave Palo Alto, CA 94304, USA [email protected]
-Franz Färber SAP Dietmar-Hopp-Allee 16 69190, Walldorf, Germany [email protected]
-Wolfgang Lehner SAP Dietmar-Hopp-Allee 16 69190, Walldorf, Germany [email protected]
-Sang Kyun Cha SAP 63-7 Banpo 4-dong, Seochoku 137-804, Seoul, Korea [email protected]
-Thomas Peh SAP Dietmar-Hopp-Allee 16 69190, Walldorf, Germany [email protected]
-Christof Bornhövd SAP 3412 Hillview Ave Palo Alto, CA 94304, USA [email protected]
2.Efficient Transaction Processing in SAP HANA Database
Presented by Henggang Cui 15-799b Talk
3. The SAP HANA Database–An Architecture Overview
-Franz F¨arber Norman
![Page 29: Efficient transaction processing in sap hana](https://reader031.fdocuments.in/reader031/viewer/2022021500/58e93f7a1a28ab84768b5b97/html5/thumbnails/29.jpg)
END
ANY QUESTIONS ?