1. Data Management Conference SQL Server for SAP Roger Holder roger.holder@microsoft.com London September 29th

2. Agenda Microsoft & SAP Fact or Fiction? −Reason #1 – Scalable −Reason #2 – Secure −Reason #3 – Availabile −Reason #4 – Large Data Volumes −Reason #5 – Lower TCO Summary Want to Know More?

3. Microsoft & SAP Direction and Strategy

4. Microsoft-SAP Alliance Microsoft runs SAP & SAP runs Microsoft Joint Microsoft-SAP development teams −SAP & Microsoft development engineers in Redmond & Walldorf −Product Enhancements −Best Practices Joint Support Agreement −Engineers located in Redmond & Walldorf SAP Competence Centre located in Walldorf −Certification −Benchmarking −Alliance Team −Migration Services

5. Microsoft Solutions for SAP Reach & Value ROI & Agility Increasing Productivity with a Familiar Environment (Duet, MOSS, OBA) Extending SAP Solutions (.NET, BizTalk) Optimizing the SAP Infrastructure (Windows, Hyper-V, SQL Server) Driving Business Performance (MS & SAP BI)

6. Fact or Fiction? Or 5 reasons why SQL Server is a viable platform for today’s Enterprise SAP landscapes

7. Market Data 65,000+ SAP deployments on Windows Server – over 57% of existing installs. 2/3 of all new SAP installations are on Windows Server. 40,000+ SAP deployments on SQL Server and growing. SQL Server has enterprise class scalability, performance and high availability. SQL Server seen to offer a TCO advantage over Oracle and DB2. Source: SAP

8. Reason #1 Enterprise Scalability

9. SAP On SQL Server Customers

10. SAP Performance on SQL Server (1) Certification Number 2003039: SAP SD standard R/3 Enterprise 4.70 application benchmark in 3-Tier configuration certified on July 14, 2003 with Number of benchmark users & comp.: 11,200 SD (Sales & Distribution) with an average dialog response time: 1.90 seconds running Windows 2003 Enterprise Edition SQL Server 2000 on RDBMS database server. Configuration: RDBMS server: HP ProLiant Model DL760 G2, 8-way SMP, Intel Xeon MP, 2.8 GHz, 2 MB L3 cache, 8 GB main memory. For more details, see http://www.sap.com/benchmarkhttp://www.sap.com/benchmark (2) Certification Number 2005030: SAP SD standard R/3 Enterprise 4.70 application benchmark in 3-Tier configuration certified on June 27, 2005 with Number of benchmark users & comp.: 18,000 SD (Sales & Distribution) with average dialog response time: 1.87 seconds running Windows Server 2003 Enterprise Edition (64-bit) and SQL Server 2005 (64-bit) on RDBMS server. Configuration: Database server: HP ProLiant DL585, 4-way SMP, Dual-core AMD Opteron processor Model 875 (2.2 GHz), 128 KB L1 cache, 2 MB L2 cache, 32 GB main memory. For more details, see http://www.sap.com/benchmarkhttp://www.sap.com/benchmark (3) Certification Number 2008003: SAP SD standard SAP ERP 6.0 (2005) application benchmark in 3-Tier configuration certified on 02/26/08 with Number of benchmark users & comp.: 34,000 SD (Sales & Distribution) with an average dialog response time: 1.99 seconds running Windows Server 2008 Enterprise Edition (64-Bit) and SQL Server 2008 (64-bit) on RDBMS database server. Hardware configuration of RDBMS server: HP ProLiant BL680c G5, 4 socket/16 core/16 thread Quad-Core Intel Xeon E7340 / 2.40GHz, 64GB RAM. For more details, see http://www.sap.com/benchmarkhttp://www.sap.com/benchmark HP BL680C Blade Server 4-Processors Quad-Core Intel® Xeon® 7300 series processor Concurrent Users (1) (2)(3) World Record Scale (3)  SQL Server 2008 on 4-Socket Industry Standard Blade servers in 3-Tier SAP SD Standard Application Benchmark Test (3)  Demonstrated throughput on Industry- Standard hardware is expected to cover scalability needs of at least 97% of all SAP deployments worldwide

11. Reason #2 Secure

12. Security Vulnerabilities # of Common Vulnerabilities and Exposures Notes: Update as of 10/15/2008. Vulnerabilities are included for SQL Server 2000, SQL Server 2005, SQL Server 2008. Oracle (8i, 9i, 9iR2, 10g, 10gR2,11g) Source: NIST National Vulnerability DatabaseNIST National Vulnerability Database

13. SQL Server Compliance Key Criteria Security functions: Access control, audit, management, identification & authentication, session handling and memory management Assurance components: Functional specs and high level design plus independent vulnerability testing Environment: CC certified OS (Windows Server) and admin roles Common Criteria Certification −Requirement for many governments, industries and enterprise customers − −SQL Server 2008 Enterprise achieved Common Criteria (CC) compliance at EAL1+ (Evaluation Assurance Level) −Represents the third time for CC compliance and the first time for a 64-bit version of SQL Server −In formal evaluation at EAL4+ and for compliance with NSA DBMS Protection Profile V1.2

14. Reason #3 Highly Available

15. SQL Server – HA features Microsoft Failover Cluster implementation −Automatic Failover −Virtual SQL Server instance −Multiple instances possible −Up to 8 nodes DB Mirroring −Automatic failover (with witness) −Second copy of a database on second storage Log Shipping −Shadow database on second location −Time delay possible −Long distance copy

16. Microsoft Failover Clustering Multiple-Instance Database Clustering More than one passive node available to host instances while performing maintenance on active nodes Multiple instances can share the same failover node, which reduces hardware costs Simple administration makes it easy to move instances to perform maintenance on passive nodes OfflineOfflineFailoverFailoverActiveActive 1100101 0010111 0010100 101 110010 110010 1100101 00101 1100101 00101 110010 ActiveActiveActiveActive

17. ABAP Central Services (ASCS) SPOF‘s SAP 7.00 (ABAP) Primary Application Server SPOF‘s: −IP Address −Hostname −Message Server −Enqueue Server −sapmnt Share −Disk with \usr\sap\ \SYS directory Spool WP Dialog WP Batch WP Update WP Message Server ABAP Dispatcher GatewayGateway IP Address and Hostname \\sapmnt\\sapmnt S:\usr\sap\<SID>\SYSS:\usr\sap\<SID>\SYS Enqueue Server

18. Replicated Enqueue Service Enqueue lock entries are hold in shared memory on the server Loss of lock entries requires roll back of open business transactions Based on the Cluster functionality of the SCS instance Central Services Instance (SCS) Message Server Enqueue Server Enqueue Replication Server (ERS) Enqueue Server Enqueue Lock table Enqueue Lock table Replication

19. MSFC Solution NW7.0 (ABAP) Quorum Disk MSSQL Data files MSSQL Log files SAP files (\\sapmnt) Cluster Group Virtual Name MSCS Node AMSCS Node B Virtual ASCS Hostname Virtual ASCS Hostname SAP Group ABAP SCS Virtual DB Hostname Virtual DB Hostname MSSQL Group Database Instance ABAP AS ERSERSERSERS

20. SAPMNT Share and Junctions SAPSID SQL Data files SAPSID SAP directories SAPSID SQL Log files SAPSID SQL Data files SAPSID SQL Data files SAPSID Quorum Shared storage Windows MSCS Software Database program files \usr\sap\ \[Junction] ….. \usr\sap\ \[Junction] Windows MSCS Software Database program files \usr\sap\ \[Junction] ….. \usr\sap\ \[Junction] Windows MSCS Software Database program files \usr\sap\ \[Junction] ….. \usr\sap\ \[Junction] Windows MSCS Software Database program files \usr\sap\ \[Junction] ….. \usr\sap\ \[Junction] Local Disk \\sapmnt share

21. Maintain Instance Performance Resource Governor Workloads can be prioritized −Prevents runaway processes from monopolizing resources and impacting production systems Establish service-level agreements (SLAs) with customers for predictable response times Deliver consistent user experience LIMIT 50% LIMIT 30% LIMIT 20% 1100101 00101 1100101 00101 110010 LOAD 25% 1100101 00101 1100101 00101 110010 LOAD 45% 1100101 00101 1100101 00101 110010 LOAD 15%

22. Reason #4 Large Data Volumes

23. SAP Data Volumes Increasing Pilgrims Pride – 12TB ERP FEMSA – 10 TB ERP E.Land – 9.6 TB ERP TUV Nord – 9.5TB ERP Microsoft – 6.5TB ERP

24. SQL Server Data Compression −Up to 60% compression ratios (Avg) −Provides both ROW and PAGE compression −Allows greater density and lower cost per gigabyte for data storage −Reduced data size can increase SAP performance −Mitigates impact of UNICODE 1001010 0101001 0100001 1111011 0101001

25. Data Compression with SAP Customer reference: Quanta Computer Gains 80 Percent Data Compression for SAP with SQL Server 2008 http://www.microsoft.com/casestudies/Case_Study_Detail.aspx?CaseStudyID=4000003962

26. SAP Pre-Requisites SQL 2008 ROW + PAGE Compression −SAP supports SQL 2008 on Kernel 7.0 or higher −ECC 6.0 SR3 & NW 7.0 SR3 or higher −Install as ROW compressed by default (no admin intervention needed) −Migrations to SQL Server can load all tables into SQL Server ROW compressed −Latest version of OSS Note 991014 should be implemented

27. Reason 5 Lowest Total Cost of Ownership

28. Demonstrated TCO 1 Server… 5,155 Concurrent Users Retail Cost of Server: $28K

29. TCO Comparison for SAP/ERP Independent study confirms migrating SAP/ERP to SQL Server pays big dividends Customer Scenarios  68 SAP/ERP customers running on different platforms:  Oracle on UNIX & Windows  DB2 on UNIX  SQL Server on Windows Downtime reduction > 20% 20-25% savings IT Admin. Labor 20-25% savings IT Incident Management Labor 61-86% savings Software Support Download study at http://www.microsoft.com/isv/sap/http://www.microsoft.com/isv/sap/ Migrating SAP/ERP to SQL Server drives down costs… …resulting in 30-37% ongoing annual savings and payback period as short as 9 months! The larger the implementation, the larger the percentage of savings! Medium ScenarioLarge Scenario Company Size$1.4B revenue, 3,000 employees $16B revenue, 40,000 employees # ERP Modules24 DB Size540 GB4800 GB Named Users2995,800 Dialog Steps/Day (millions of txns.) 1.95.9 SLA99.5% SLA99.99% SLA

30. SAP Platform Cost Savings Migrating an SAP/ERP environment to SQL Server −Can reduce unplanned downtime by over 20% −Cut IT labour costs by nearly 25% −Cut ongoing software support costs up to 85% Migration from competitive databases made easy by tools, best practices, and certified SAP migration specialists −Payback is as short as nine months −Ongoing annual savings of 30%-37% possible † “Microsoft SQL Server Migration Pays Big Dividends for SAP/ERP Customers, Wipro, Feb 2008”

31. Summary SQL Server 2008 Runs SAP

32. SAP Feature Summary SQL Server 2005 Database Mirroring Online Index Operation Monitor Query Performance Monitor Index Usage SQL Server 2005 Table Partitioning Improvements in Backup/Recovery Database Snapshots Scalability/Flexibility SQL Server 2008 Mirroring Log compression, Auto repair Partition Parallelism enhancement Backup Compression Compression (row, page) Star Join Optimization Encryption of data files transparent to SAP Improved locking, logging Performance Data Collection

33. The Last Word……from SAP Viable Reliable Cost-Effective Proven Strong Partnership Enterprise Class Optimal TCO “With a market leading price/performance ratio, SQL Server supports demanding SAP customers with a competitive solution. −Optimal Solution for SAP customers of all sizes −SQL Server can run the workload of all competitors (including Oracle)”

34. Want to Know More? Administering SAP Solutions on Microsoft SQL Server 2008 −3-Day, hands-On, and deep technical training −Covering: −System Sizing −Installation −High Availability −Disaster Recovery −Backup and Restore −Best Practices Configuration −Performance Tuning Course Availability: −November 17 th – 19th −May 5 th – 7 th 2010

35. Thank You! Learn more about SQL Server 2008 −http://www.microsoft.com/sql/2008/default.mspxhttp://www.microsoft.com/sql/2008/default.mspx Learn more about SAP on SQL Server −http://www.microsoft.com/sap/sql/default.mspxhttp://www.microsoft.com/sap/sql/default.mspx Windows & SQL Server on SDN: −https://www.sdn.sap.com/irj/sdn/msshttps://www.sdn.sap.com/irj/sdn/mss

36. © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.