Your SlideShare is downloading. ×
Why Exadata for SAP? - Michał Kostrzewa
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Why Exadata for SAP? - Michał Kostrzewa

1,696
views

Published on

Published in: Technology

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,696
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Why Oracle Exadata for SAP ?- Todays Challenges and Benefits Provided Michał Jerzy Kostrzewa (Michal.Kostrzewa@Oracle.com) ECE Business Development Manager
  • 2. Agenda • Todays Challenges within the DB-tier <Insert Picture Here> • Exadata Software Features • Benefits for SAP CustomersCopyright © 2010, Oracle Corporation and/or its affiliates –2–
  • 3. Challenges Within the Database Tier • Increasing database workloads in terms of: volume, throughput and response times  but typical SAP architecture is still 3tier SCSI Block I/O • Service up-time requirements have grown whereas classical solutions for HA ... 3) DB  are complex and costly  are spanned across multiple vendors & SQLNet products 2) App  may not meet all Recovery-Time-Objectives • Cost for deployment and operation DIAG  high ongoing effort to tune and optimize SQL statements, database, storage array and 1) GUI storage network  little/no consolidation of database serversCopyright © 2010, Oracle Corporation and/or its affiliates –3–
  • 4. The Major Shift: Evolving the Architecture Instead of Deploying Just a Faster DB-Server • Moving from 3tier to 4tier architecture 4) Storage  take storage layer into consideration: Grid push SQL processing to the data (/storage layer) iDB  scale-out on database tier  process more requests in parallel 3) DataBase Grid • Use state-of-the-art technology  low latency / high performance network SQLNet  flash storage to accelerate disk IO 2) App • Deploying pre-configured, turn-key system consolidating dozens of databases DIAG  integrates database and storage layer  optimized for high performance & availability 1) GUI  < 2 weeks deploymentCopyright © 2010, Oracle Corporation and/or its affiliates –4–
  • 5. Exadata is Smart Storage Storage Server is a smart storage device, not a DB node Compute and Memory Intensive Processing  Database Servers  Perform complex database processing such as SQL parsing, SGA buffer lookups, joins, aggregations, etc.  Exadata Storage Servers  Search tables and indexes filtering out data that is not relevant to a query  Cells serve data to multiple databases Data Intensive enabling consolidation, i.e. OLTP and OLAP Processing workload  Simplicity, and robustness of storage applianceCopyright © 2010, Oracle Corporation and/or its affiliates –5–
  • 6. Exadata Software Traditional Processing SAP Application DB Server Storage Array Server How many Requesting IO articles 4711 are Single operations, ordered in client sequential SCSI filtering result 010 by sales org block IO of 8k set 15 ? Select sum(kwmeng) from VBAP where VBAP has 800 GByte in size: matnr=’4711’ and... - 800 GB are read from disk over the SAN - 800 GB are transferred into DB server main memory - 20 GB of data is matching filter criteria - sum of order quantity is sent back to the application server (< 1KByte)Copyright © 2010, Oracle Corporation and/or its affiliates –6–
  • 7. Exadata Software Smart Scan Offload Processing SAP Application Exadata DB Exadata Server Server Grid Storage Grid How many Smart Scan Smart Scan articles 4711 are identifies rows constructed and ordered in client and columns sent to the 010 by sales org that match storage cells 15 ? request Select sum(kwmeng) from VBAP where VBAP has 800 GByte in size: matnr=’4711’ and... - 800 GB of data is retrieved by all storage cells in parallel from Flash or disk - each cell server checks query match - sum order quantities are sent back to the DB grid (few Kbytes) - DB server adds up and returns total sumCopyright © 2010, Oracle Corporation and/or its affiliates –7–
  • 8. Exadata Software Storage Indexing Table Index  Exadata Storage Indexes maintain summary information about table data in A B C D memory 1  Store MIN and MAX values of columns Typically one index entry for every MB of disk Min B = 1  3 Max B = 5 5  Eliminates disk I/Os if MIN and MAX can never match “where” clause of a query 5 Min B = 3 8 Max B = 8  Completely automatic and transparent 3 Select * from Table where B<2 - Only first set of rows can matchCopyright © 2010, Oracle Corporation and/or its affiliates –8–
  • 9. Exadata Software Smart Flash Cache Technology Exadata has 5 TB of cache on PCI cards  56 PCI cards avoid disk controller bottlenecks  less latency compared to SSDs  75,000 IOPs/cell or 1 million IOPS per Exadata rack  can be used as Exadata Flash-based storage (persistent), as Exadata Smart Flash Cash (default) or a combination of it Intelligently manages flash  software understands different types of database IO  not caching IO from mirror copies, backups, formatting, statistics runs, etc.  avoids large scans monopolizing the cacheCopyright © 2010, Oracle Corporation and/or its affiliates –9–
  • 10. Exadata Software Hybrid Columnar Compression  Tables are organized in sets of few thousands rows (compression unit)  Within a compression unit data is organized and compressed by column  dramatically better compression (13 X in average)  Speed-optimized Query Mode for Data Warehousing benefits from  columnar storage  Exadata offload features  Data update requires uncompress & recompress => Not to be used for frequently updated data  Read-only InfoCubes in SAP BW are a good fit for HCC Usage of Hybrid Columnar Compression requires SAP approvalCopyright © 2010, Oracle Corporation and/or its affiliates – 10 –
  • 11. Exadata Storage Software Unique Features for SAP Exadata Smart Scans 1) Great reduction in data sent to database servers Offloading data processing to storage cells Exadata Storage Indexes 1) Eliminate unnecessary I/O Hybrid Columnar Compression 2) Efficient compression increases effective storage capacity and increases user data scan bandwidths by a factor of up to 10X Exadata Smart Flash Cache Breaks random I/O bottleneck by increasing IOPs by up to 20X Doubles user data scan bandwidths I/O Resource Manager (IORM) Enables storage grid by prioritizing I/Os to ensure predictable performance Quality of Service (QoS) Actively meet and maintain SLAs Memory Guard to protect existing current transactions from memory-based failures 1) Limited use with SAP applications as data is mainly accessed through indexes 2) Hybrid Columnar Compression can be used but no SAP support is providedCopyright © 2010, Oracle Corporation and/or its affiliates – 11 –
  • 12. Exadata – Benefits For SAP Customers •Faster Response Times Extreme •More Throughput Performance •Faster Business Decisions on More Data •Consolidate Database Platforms High Efficiency •Reduce Effort for Tuning & Optimization in Operations •Lowering Time-To-Deploy and Risk • No Downtime after Loss of DB Instance Increased Uptime • Relocation of DB load possible • No Impact after Loss of SAP SCSCopyright © 2010, Oracle Corporation and/or its affiliates – 12 –
  • 13. Why is Exadata So Fast? • Scaling-out & Parallelization of Tasks  RAC  multiple storage servers are processing one query in parallel  SAME (stripe-and-mirror-everywhere) principle with ASM • Extensive Use of Flash Cache (NAND on PCI cards)  minimizes physical disk IO  overcomes disk controller bottlenecks • High-Throughput / Low Latency Network  between storage & database servers  speeds-up Global Cache communication (RAC) • Exadata Data Storage Software  delegates parts of the processing to the storage layer  intelligent / application-aware use of flashCopyright © 2010, Oracle Corporation and/or its affiliates – 13 –
  • 14. Exadata – Benefits For SAP Customers •Faster Response Times Extreme •More Throughput Performance •Faster Business Decisions on More Data •Consolidate Database Platforms High Efficiency •Reduce Effort for Tuning & Optimization in Operations •Lowering Time-To-Deploy and Risk • No Downtime after Loss of DB Instance Increased Uptime • Relocation of DB load possible • No Impact after Loss of SAP SCSCopyright © 2010, Oracle Corporation and/or its affiliates – 14 –
  • 15. Exadata for Database Consolidation Consolidation is key to SAP HR • reducing costs: administration, hardware, software, floor space SAP BW • increasing agility: same day database deployments (e.g. sandbox systems) SAP ECC • Suitable for different sizes & environments: • multiple small databases within one node SAP DEV • large databases can span nodes using RAC SAP QAS • production, development, QAS, ... • Accomodates different workloads: DataMart • OLTP, DataWarehouse, unstructured/Blobs • SAP and non-SAPCopyright © 2010, Oracle Corporation and/or its affiliates – 15 –
  • 16. Builtin Function Supporting Consolidation • IO Resource Management  limits the number of outstanding IO requests  prevents low-priority intensive workloads flooding the disk  “resource plans” reserve bandwidth between databases and within a database • Instance caging  fencing CPU utilization when multiple databases are running the same database server node • Security  manages access from databases to ASM Grid disks  on ASM cluster level and database levelCopyright © 2010, Oracle Corporation and/or its affiliates – 16 –
  • 17. Exadata – Benefits For SAP Customers •Faster Response Times Extreme •More Throughput Performance •Faster Business Decisions on More Data •Consolidate Database Platforms High Efficiency •Reduce Effort for Tuning & Optimization in Operations •Lowering Time-To-Deploy and Risk • No Downtime after Loss of DB Instance Increased Uptime • Relocation of DB load possible • No Impact after Loss of SAP SCSCopyright © 2010, Oracle Corporation and/or its affiliates – 17 –
  • 18. Business Continuity for SAP Any single point of failure of an SAP system removed by Oracle SAP ERP • DB services always up and running: • redundant hardware components SAP CRM • Oracle RAC (Real Application Cluster) • CRS (Clusterware) SAP BW • TAF (Transparent Application Failover) Warehouse • SAP SCS protection through CRS and Enqueue Replication Data Mart • Mirroring main memory content (transaction lock table) to secondary server HR • Instantaneous fail-overCopyright © 2010, Oracle Corporation and/or its affiliates – 18 –
  • 19. Copyright © 2010, Oracle Corporation and/or its affiliates – 19 –