Written by Donald Feinberg and Merv Adrian
On 25-Sep-2017 at Ignite, Microsoft announced general availability of SQL Server 2017, now supporting both Windows and Linux platforms, as well as support for containers. It can now book revenue for a product already widely used by early release customers.
What does this imply for the $34.4 billion database management system (DBMS) Market? Over the years, Microsoft has grown SQL Server revenue substantially, capturing over 20 percent of the DBMS market without a Linux offering. Few thought we would see the day where a major Microsoft software product would run on anything other than Windows.
Microsoft SQL Server started life as Sybase SQL Server. In 1988, Microsoft acquired joint rights on x86 and called it SQL Server. In 1993, the partnership was dissolved and Microsoft retained SQL Server and developed it independently of Sybase, running on x86 and Windows OS. SAP ASE, formerly Sybase ASE, (Sybase was acquired by SAP in 2010) shares the procedural language Transact-SQL (T-SQL) with SQL Server.
Linux support has been a long time in coming. Both of us were in (separate) meetings at Microsoft 10 or 12 years ago, where we suggested that SQL Server be ported to Linux. The notion was met by the senior management of the then Server & Tools Group (STG) with strong disagreement (and several “expletives deleted.”). Our premise then – and still – was that this would position SQL Server as a portable DBMS, boosting sales, offering more addressable market to compete in. Customers would know they could move to Linux if desired, removing the notion of lock-in to the Windows Server OS.
Today, SQL Server runs on Windows and Linux – and containers (Docker and Kubernetes), putting it on an equal footing with other DBMS products. It supports Availability Groups that span both OSs, enhancing cross-OS testing and migration projects. Microsoft claims over 2 million Docker pulls of SQL Server 2017 for Linux since November 2016. With the generally lower pricing of SQL Server, including availability on-premises with a subscription instead of a license + maintenance, as well as pricing and discount programs including a joint marketing program with Red Hat (see Microsoft’s press release), we expect increased competition with other relational DBMS players, like IBM Db2, Oracle and SAP ASE.
The momentum is clear. Gartner Software Market numbers show that Microsoft passed IBM in total DBMS revenues in 2014 and is now second only to Oracle. In 2016 overall DBMS revenues grew at 7.7 percent and Microsoft grew at 10.3 percent, strengthening its #2 position, while Oracle grew 3.3 percent – off a much larger base that includes the Linux workloads Microsoft did not compete for. With a competitively priced product that is now portable across more than one operating system, Microsoft SQL Server is positioned to gain even more market share. To further support this, SQL Server on-premises is now fully compatible to Azure SQL Database, allowing customers full flexibility in choosing the desired platform, using on-premises SQL Server licenses for Azure deployments. Its on-premises subscription pricing positions it competitively with open-source RDBMS products, with no upfront license fees. In the year ahead, competition will be more heated than is has been for years.
Read Complimentary Relevant Research
100 Data and Analytics Predictions Through 2021
Over the next few years, data and analytics programs will become even more mission-critical throughout the business and across industries....
View Relevant Webinars
Digital Business Architecture: From Strategy to Guiding Execution
New techniques have emerged to help CIOs and EA practitioners leverage business architecture to guide investment and execution decisions,...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.