DBMS Market: State Of The Union

1. Webinar DBMS Market: State Of The Union Noel Yuhanna, Principal Analyst September 18, 2012. Call in at 12:55 p.m. Eastern time September 18th, 2012. Call in at 12:55 p.m. Eastern time

2. Database requirements are changing. Is your strategy in place?

3. Agenda • Current drivers and trends impacting database • Key DBMS vendors • Your enterprise database strategy in 2012–2013 • Recommendations

4. New applications are changing database requirements • Social networking apps • Mobile applications • High-performance apps • Real-time apps • Real-time data mashup • Departmental and collaboration • Predictive analytics Real-time data Non-structured data Faster access

5. Database appliances are here to stay High performance Integrated Scalable Single vendor Automated Improved SLAs Cost-effective? Vendor lock-in?

6. Falling memory prices and new in-memory technologies offer new possibilities In-memory database Falling memory prices 1. Memory price, which was $100,000/GB in 1990, is down to $5/GB in 2012. 2. Data stored in cache/memory can be accessed 20x to 50x faster than data stored in disk. 3. In-memory database and distributed cluster delivers powerful horizontal scale.

7. Public cloud databases are viable to support moderate-size applications On-demand scale Easy to provision Automated Database Cost effective Backup Highly available Security Latency Integration 7

8. Databases need to support more than structured relational data — be prepared • You need more than RDBMS! • Hadoop can help . . . • NoSQL DBMS can help . . . Structured Unstructured Semi-structured

9. Hadoop can help process large amounts of data that’s difficult to do in databases • Open source software that enables distributed parallel processing of large amounts of data across low-cost commodity servers. • It leverages an extensible framework for building advanced analytics and new data management capabilities. • It’s already being commercialized and adopted rapidly in enterprises. Large amounts of data Hadoop Flexible Distributed processing Scalable Economical Open source Insights

10. NoSQL — gains momentum • What is NoSQL? • NoSQL is a non-relational database. • Why use it? • Cost, performance, scale, and availability • Why not use it? • Maturity, complexity, manageability, staffing, and support • Five key categories for NoSQL: Document DB Key-value store Tabular Graph DB Object DB

11. NoSQL options Key-value store 10gen/MongoDB, Apache Cassandra, Dynamo, Basho/Riak,InterSystems Cache, Freebase, Citrusleaf, Oracle Coherence Redis, Tuple space, Oracle Berkeley DB, Informix C-ISAM, andMemcacheDB Document database Apache CouchDB, MarkLogic, MongoDB, SimpleDB, Terrastore,Recall, Jackrabbit, eXist, and Clusterpoint Graph database DEX, Infinite Graph, Neo4j, OrientDB, FlockDB, Pregel, Sones GraphDB, CloudGraph, GraphBase, HyperGraph, IBM/GraphStore, InfoGrid, VertexDB, Virtuoso, and OrientDB

12. NoSQL options (cont.) Tabular Big Table, Apache, Hadoop, Apache Hadoop, Apache HBase, and Hypertable Object database Db40, Gemstone, InterSystems Cache, ObjectDB,Objectivity/DB, and Versant

13. Agenda • Current drivers and trends impacting database • Key DBMS vendors • Your enterprise database strategy in 2012–2013 • Recommendations

14. Top enterprise DBMSes

15. MySQL: losing its charm Strengths Still has a large open source database community Still has a high rate of adoption among all open source databases Largest ecosystem for open source database Weaknesses Oracle’s lack of strong push compared with Oracle DBMS No new innovative features with MySQL Migration from other DBMS: tools, approach Support for very large databases remains weak. Customers are bailing out — to what?

16. PostgreSQL takes over where MySQL left off • Strengths • Good DBMS technology and features (been around for decades) • Good support for transactions and decision-support environments • Reliable and stable open source database product • Second largest community after MySQL — and it’s growing, unlike My SQL. • EnterpriseDB and VMware support PostgreSQL. • Weaknesses • Had been leaderless, trying to get back in the race — previously SUN and now EnterpriseDB Corporation and VMware • Ecosystem still lagging behind — tools, apps, partners — but that’s changing • High-end scale still a concern

17. Actian-Ingres offers a viable open source DBMS • Strengths • Ingres 10 — MVCC, migration from MySQL-Oracle-SQL-Sybase, column-encryption, geospatial support, improved performance • Good DBMS technology and features (has been around for decades) • Good support for transactions and decision-support environments • Reliable and stable open source database product • Established more than 10,000 customers using Ingres • Weaknesses • Lack of strong innovation • Name change — has had some impact on Ingres • High-end scale still a concern • Migrations still not that simple

18. Sybase gains some traction but still has some ways to go to become a dominant player Strengths Acquisition by SAP — helping to become more visible Integration with SAP — apps, tools, and middleware — preferred DB? Strong replication product that is heterogeneous — Oracle, DB2, etc. Remains innovative — data-at-rest encryption, ASE clustering SAP HANA — gaining momentum Integration of SAP-Sybase technology Weaknesses Shortage of Sybase skills Performance/scale issues

19. IBM DB2 puts pressure on Oracle and others to gain stronger momentum • Strengths • DB2 10 is out — performance improvements, time travel query, NoSQL graph store, multi-temperature data management, improved compression • IBM DB2 is back with increased adoption and growth. • Compatibility layer with DB2 9.7+ good success so far • Best database for XML, compression is DB2 • High performance and good scale — Purescale • Acquisition of Netezza helps IBM to offer appliances. • Increased deployment of appliances • Weaknesses • Adoption of DB2 in Windows and Linux? • Cloud?

20. Microsoft SQL Server gains traction but is still lagging in the high-end deployments Strengths SQL Server 2012 has some good points — AlwaysOn, improved performance and automation, xVelocity, data tools . . . Support for Big Data/Hadoop Easy-to-use and strong in manageability Integration with application development — versus .NET — EDM Cloud database — SQL Azure — strong adoption Good security features and lowest vulnerabilities, detailed auditing SQL Server on Hyper V — strong integration Weaknesses Adoption of Parallel Data Warehouse (PDW) is slow. High-end performance — scale-out

21. Teradata offers strong data warehouse platform • Strengths • Highly scalable and flexible EDW solution • Strong install base, revenue, and momentum in EDW market • Continues to innovate — geospatial, real-time, in-database analytics, SSD, unstructured data • Several form factor — licensed software, pre-integrated appliance, cloud/SaaS, and virtualized offerings • Strong support for in-database analytics, caching, compression,partitioning, indexing, workload management, and query optimization • Weaknesses • Database integration — relies mostly on partners for supplementary technology • Can be expensive

22. Oracle dominates the market — continues innovation • Strengths • Oracle Exadata has got legs — 1,000-plus customers? • Oracle 12c releasing this year • Has dramatically improved manageability and self-managing features • High-end performance — improved • In-memory cache gaining grounds • NoSQL offering, big data appliance, apex • Weaknesses • Add-on options — cost concern for enterprises • Windows adoption still weak but improving compared with last year • Scale-out sharded database model?

23. Agenda • Current drivers and trends impacting database • Key DBMS vendors • Your enterprise database strategy in 2012–2013 • Recommendations

24. How to improve database performance New New New

25. How to improve availability New New

26. Dealing with high volume of data? New New New

27. How to lower the cost of your DBMS New New New New

28. How many DBAs do you really need? Average tends to be 35:1 database-to-DBA ratio Best ratio is with SQL Server — 46:1. Oracle is at 25:1 average. DB2 and Sybase are in the middle with 33:1 and 35:1. Cap is roughly 12TB size collectively. Seen as high as 265 database-to-DBA Recommendations: Create your baseline. Improve on the baseline — check every six months. Tools, cloud, and appliance can help.

29. Agenda • Current drivers and trends impacting database • Key DBMS vendors • Your enterprise database strategy in 2012–2013 • Recommendations

30. Recommendations 1. DBMS can handle multiple terabytes of data (40TB for, 250TB for DW). For more, look beyond relational, appliances, or in-memory technologies. 2. 80% of your apps can be supported by any of the top RDBMS products; 20% need a new approach — such as NoSQL, XML DB, open source, etc. (scale-out sharding, schema-less architecture, document database, etc.). 3. Look at upgrading to newer releases to reduce administration cost and improve availability. 4. Database appliances should be a part of your DBMS strategy. 5. In-memory is critical — if you don’t have it, you are missing out on something big! 6. To lower cost, look at cloud database, database consolidation, clustering, standardization of DBMS, and automation.

31. Noel Yuhanna +1 650.581.3807 nyuhanna@forrester.com