History of Microsoft SQL Server: Difference between revisions

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Revision as of 09:33, 31 May 2025 edit Ylee (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 48,241 edits →SQL Server 7.0: Becomes Oracle's top competitor ← Previous edit		Latest revision as of 22:49, 22 August 2025 edit undo 1234qwer1234qwer4 (talk \| contribs) Extended confirmed users, Page movers 206,939 edits +Category:Software topical history overviews; +Category:Software version histories using HotCat
(4 intermediate revisions by 3 users not shown)
Line 178: \|15.0 \|November 4, 2019 \|{{version\|coo\|January 14, 2025}} \|{{version\|co\|January 8, 2030}} \|SQL Server 2019 Line 198: ==Detailed history== ===Genesis=== InBy the late 1980s [[Microsoft]] was interested in the low end of the [[database software]] market, while [[Sybase]] focused on the [[Fortune 1000]]. After the former discussed a partnership with Sybase rival [[Informix Corporation]],<ref name="rdbmsingressybase20070613">{{Cite interview\|interviewer=Doug Jerger\|title=RDBMS Workshop: Ingres and Sybase\|url=https://archive.computerhistory.org/resources/access/text/2013/05/102702565-05-01-acc.pdf\|access-date=2025-05-30\|publisher=Computer History Museum\|date=2007-06-13}}</ref> in January 1988 Microsoft joined [[Ashton-Tate]] and [[Sybase]] to create a variant of [[Sybase SQL Server]] for [[IBM]] [[OS/2]] (then developed jointly with Microsoft) compatible with Ashton-Tate's [[dBASE]] software. [[Information Builders]], [[Borland]], and [[Symantec Corporation]] announced support for the product. Microsoft's [[Bill Gates]] praised Sybase as the best SQL database engine, and persuaded Ashton-Tate to use it instead of its own. Rivals such as [[Microrim]] ([[R:Base]]), [[Novell]], [[Oracle Corporation]], and [[Lotus Development]] said that they would use their own technology, or that they expected IBM's own SQL technology in OS/2 Extended Edition to be the standard.{{r\|mace19880118}} Scheduled for the second half of 1988,<ref name="mace19880118">{{Cite magazine \|last=Mace \|first=Scott \|date=18 January 1988 \|title= Ashton-Tate, Microsoft Join Forces To Introduce SQL Database Server\|url=https://books.google.com/books?id=Dz8EAAAAMBAJ&pg=PA1~~#v=onepage&q&f=false~~ \|access-date=2025-05-25 \|magazine=[[InfoWorld]] \|pages=1,8 \|volume=10 \|issue=3}}</ref> it was released in 1989.<ref>{{cite book\|last=Harris\|first=Scott\|author2=Curtis Preston\|title=Backup & Recovery: Inexpensive Backup Solutions for Open Systems\|url=https://books.google.com/books?id=M9mbAgAAQBAJ&q=origins+of+SQL+Server+Sybase&pg=PA562\|year=2007\|publisher=O'Reilly\|isbn=978-0596102463\|page=562}}</ref> This was the first version of Microsoft SQL Server, and served as Microsoft's entry to the enterprise-level database market, competing against Oracle, IBM, Informix, Ingres and later, Sybase. SQL Server 4.2 was shipped in 1992, bundled with OS/2 version 1.3, followed by version 4.21 for [[Windows NT]], released alongside Windows NT 3.1. SQL Server 6.0 was the first version designed for NT, and did not include any direction from Sybase. Sybase revenue grew quickly during the late 1980s from the Microsoft relationship.{{r\|rdbmsingressybase20070613}} About the time [[Windows NT]] was released in July 1993, Sybase and Microsoft parted ways and each pursued its own design and marketing schemes. Microsoft negotiated exclusive rights to all versions of SQL Server written for Microsoft operating systems. (In 1996 Sybase changed the name of its product to [[Adaptive Server Enterprise]] to avoid confusion with Microsoft SQL Server.) Until 1994, Microsoft's SQL Server carried three Sybase copyright notices as an indication of its origin. ===SQL Server 7.0=== [[File:Microsoft_SQL_Server_7.0_Setup_Splash_Screen.jpg\|thumb\|right\|SQL Server 7.0 Splash Screen]] After problems at its main rivals, SQL Server became Oracle's most important competitor.<ref name="rdbmslateryears20070612">{{Cite interview \|interviewer=Burton Grad \|title=RDBMS Plenary Session: The Later Years \|url=https://archive.computerhistory.org/resources/access/text/2013/05/102701921-05-01-acc.pdf \|access-date=2025-05-30 \|publisher=Computer History Museum \|date=2007-06-12}}</ref> SQL Server 7.0 was a major rewrite (using C++) of the older Sybase engine, which was coded in C. Data pages were enlarged from 2k bytes to 8k bytes. Extents thereby grew from 16k bytes to 64k bytes. User Mode Scheduling (UMS) was introduced to handle SQL Server threads better than Windows preemptive multi-threading, also adding support for fibers (lightweight threads, introduced in NT 4.0, which are used to avoid context switching<ref>{{cite web\|url=https://technet.microsoft.com/en-us/library/aa175393%28v=sql.80%29.aspx\|title=Developer tools, technical documentation and coding examples}}</ref>). SQL Server 7.0 also introduced a multi-dimensional database product called SQL OLAP Services (which became Analysis Services in SQL Server 2000). SQL Server 7.0 would be the last version to run on the DEC Alpha platform. Although there were pre-release versions of SQL 2000 (as well as Windows 2000) compiled for Alpha, these were canceled and were never commercially released. Mainstream support ended on December 31, 2005, and extended support ended on January 11, 2011. Line 227: ===SQL Server 2005=== SQL Server 2005 (formerly codenamed "Yukon") was released in November 2005, introducing native support for [[x86-64\|x64]] systems and updates to Reporting Services, Analysis Services & Integration Services.<ref name="The Definitive Guide to Scaling Out SQL Server 2005">{{cite book \|author=Don Jones \|url=https://books.google.com/books?id=MhkaNTEGCdgC&pg=PA218 \|title=The Definitive Guide to Scaling Out SQL Server 2005 Edition \|publisher=realtimepublishers.com \|year=2005 \|isbn=9781931491532}}</ref> It included native support for managing [[XML]] data, in addition to [[relational database\|relational data]]. For this purpose, it defined an <code>xml</code> [[data type]] that could be used either as a data type in database columns or as [[Literal (computer science)\|literal]]s in queries. XML columns can be associated with [[XSD]] schemas; XML data being stored is verified against the schema. XML data is queried using [[XQuery]]; SQL Server 2005 added some extensions to the [[T-SQL]] language to allow embedding XQuery queries in T-SQL. It also defines a new extension to XQuery, called XML DML, that allows query-based modifications to XML data. SQL Server 2005 also allows a database server to be exposed over [[web service]]s using [[Tabular Data Stream]] (TDS) packets encapsulated within [[SOAP]] requests. When the data is accessed over web services, results are returned as XML.<ref name="Database Engine XML Enhancements">{{cite web\|url=http://msdn.microsoft.com/en-us/library/ms170809.aspx\|title=Database Engine XML Enhancements\|accessdate=December 3, 2007}}</ref> [[Common Language Runtime]] (CLR) integration was introduced with this version, enabling one to write SQL code as Managed Code by the CLR. For relational data, [[T-SQL]] has been augmented with error handling features (try/catch) and support for recursive queries with CTEs (Common Table Expressions). SQL Server 2005 has also been enhanced with new indexing algorithms, syntax and better error recovery systems. Data pages are [[checksum]]med for better error resiliency, and optimistic concurrency support has been added for better performance. Permissions and access control have been made more granular and the query processor handles concurrent execution of queries in a more efficient way. Partitions on tables and indexes are supported natively, so scaling out a database onto a [[Cluster (computing)\|cluster]] is easier. SQL CLR was introduced with SQL Server 2005 to let it integrate with the .NET Framework.<ref name="Database Engine Enhancements">{{cite web\|url=http://msdn.microsoft.com/en-us/library/ms170910.aspx\|title=Database Engine Enhancements\|accessdate=December 3, 2007}}</ref> Line 237: * DMVs (Dynamic Management Views), specialized views and functions that return server state information that can be used to monitor the health of a server instance, diagnose problems, and tune performance.<ref name="Dynamic Management Views and Functions">[http://msdn.microsoft.com/en-us/library/ms188754.aspx Dynamic Management Views and Functions. retrieved June 6, 2010]</ref> Service Pack 1 (SP1) was released on April 18, 2006, adding Database Mirroring, a high availability option that provides redundancy and failover capabilities at the database level<ref name="database mirroring">{{cite web \|date=November 20, 2007 \|title=Issues to consider when you use the database mirroring feature in the initial release of SQL Server 2005 \|url=http://support.microsoft.com/kb/907741 \|accessdate=September 4, 2011 \|publisher=Support.microsoft.com}}</ref> (Database Mirroring was included in the RTM release of SQL Server 2005, but it was not enabled by default, being supported for evaluation purposes{{citation needed\|date=June 2015}}). Failover can be manual or automatic; automatic failover requires a witness partner and an operating mode of synchronous (also known as high-safety or full safety).<ref name="Automatic Failover">{{cite web \|title=Automatic Failover \|url=http://msdn.microsoft.com/en-us/library/ms189590.aspx \|accessdate=September 4, 2011 \|publisher=Msdn.microsoft.com}}</ref> Service Pack 2 released on February 19, 2007, Service Pack 3 was released on December 15, 2008, and SQL Server 2005 Service Pack 4 released on December 13, 2010. Mainstream support for SQL Server 2005 ended on April 12, 2011, and Extended support for SQL Server 2005 ended on April 12, 2016. Line 246: Other new data types include specialized date and time types and a ''Spatial'' data type for ___location-dependent data.<ref name="iWeek">{{cite web\|url=http://www.informationweek.com/software/showArticle.jhtml?articleID=199500164&subSection=Development\|title=Microsoft Gives Peek At Next Version Of SQL Server\|accessdate=May 11, 2007\|archive-date=October 11, 2007\|archive-url=https://web.archive.org/web/20071011225111/http://informationweek.com/software/showArticle.jhtml?articleID=199500164&subSection=Development\|url-status=dead}}</ref> Better support for unstructured and semi-structured data is provided using the new ''FILESTREAM''<ref name="mary">{{cite web\|url=http://blogs.zdnet.com/microsoft/?p=937\|title=One more test build to go for SQL Server 2008\|accessdate=November 13, 2006\|archive-date=June 23, 2008\|archive-url=https://web.archive.org/web/20080623135221/http://blogs.zdnet.com/microsoft/?p=937\|url-status=dead}}</ref> data type, which can be used to reference any file stored on the file system.<ref name="Kummert">{{cite web\|url=http://blogs.msdn.com/stevengu/archive/2007/11/13/guest-blogger-ted-kummert.aspx\|title=Guest Blogger: Ted Kummert\|accessdate=November 20, 2007}}</ref> Structured data and metadata about the file is stored in SQL Server database, whereas the unstructured component is stored in the file system. Such files can be accessed both via [[Win32]] file handling [[API]]s as well as via SQL Server using [[T-SQL]]; doing the latter accesses the file data as a BLOB. Backing up and restoring the database backs up or restores the referenced files as well.<ref name="kleinerman">{{cite web\|url=http://channel9.msdn.com/Showpost.aspx?postid=387069\|title=SQL Server 2008 for developers\|author=Christian Kleinerman\|publisher=[[Channel 9 (Microsoft)\|Channel 9]]\|accessdate=March 7, 2008}}</ref> SQL Server 2008 also natively supports hierarchical data, and includes [[T-SQL]] constructs to directly deal with them, without using recursive queries.<ref name="kleinerman"/> The [[full-text search]] functionality has been integrated with the database engine. According to a Microsoft technical article, this simplifies management and improves performance.<ref name="Full-Text Search">{{cite web\|url=http://msdn.microsoft.com/en-us/library/cc721269.aspx\|title=SQL Server 2008 Full-Text Search: Internals and Enhancements\|author=Fernando Azpeitia Lopez\|date=September 4, 2009 }}</ref> Spatial data will be stored in two types. A "Flat Earth" (GEOMETRY or planar) data type represents geospatial data which has been projected from its native, spherical, coordinate system into a plane. A "Round Earth" data type (GEOGRAPHY) uses an ellipsoidal model in which the Earth is defined as a single continuous entity which does not suffer from the singularities such as the international dateline, poles, or map projection zone "edges". Approximately 70 methods are available to represent spatial operations for the Open Geospatial Consortium [[Simple Features for SQL]], Version 1.1.<ref name="Spatial Support">{{cite web\|url=http://www.directionsmag.com/editorials.php?article_id=2477&trv=1\|title=Microsoft Shares Details on SQL Server 2008 Spatial Support by Directions Staff\|accessdate=September 7, 2007\|archiveurl=https://web.archive.org/web/20070808001216/http://www.directionsmag.com/editorials.php?article_id=2477&trv=1\|archivedate=August 8, 2007\|url-status=dead}}</ref> Line 254: The final SQL Server 2008 service pack (10.00.6000, Service Pack 4) was released on September 30, 2014.<ref name="Service Pack 4">{{cite web\|url=http://blogs.msdn.com/b/sqlreleaseservices/archive/2014/09/30/sql-server-2008-service-pack-4-has-released.aspx\|website=SQL Release Services Blog\|title=SQL Server 2008 Service Pack 4 has released\|accessdate=October 1, 2014}}</ref> SQL Server 2008 had mainstream support until July 8, 2014, and extended support until July 9, 2019.<ref>{{cite web\|title=SQL Server 2008 Support Lifecycle\|url=https://learn.microsoft.com/lifecycle/products/microsoft-sql-server-2008\|website=Microsoft Product Lifecycle}}</ref> [[volume licensing\|Volume licensed]] Standard, Web, Enterprise, Workgroup and Datacenter editions of SQL Server 2008 are eligible for the Extended Security Updates program.<ref name=ESU4SQL(Doc)>{{cite web\|title=What are Extended Security Updates for SQL Server?\|url=https://learn.microsoft.com/sql/sql-server/end-of-support/sql-server-extended-security-updates\|website=Microsoft Documentation\|date=July 13, 2023}}</ref> The first term of yearly installment ended on July 14, 2020, the second term ended on July 13, 2021, and the third term ended on July 12, 2022.<ref name=SQL2008ESU(Blog)>{{cite web\|title=Announcing new options for SQL Server 2008 and Windows Server 2008 End of Support\|first=Takeshi\|last=Numoto\|url=https://azure.microsoft.com/blog/announcing-new-options-for-sql-server-2008-and-windows-server-2008-end-of-support\|archiveurl=https://web.archive.org/web/20181030193930/https://azure.microsoft.com/en-us/blog/announcing-new-options-for-sql-server-2008-and-windows-server-2008-end-of-support\|date=July 12, 2018\|archivedate=October 30, 2018\|url-status=live}}</ref><ref name=Products_with_ESU>{{cite web\|title=Lifecycle FAQ - Extended Security Updates\|url=https://learn.microsoft.com/lifecycle/faq/extended-security-updates\|website=Microsoft Documentation}}</ref> Those volume licensed editions rehosted on [[Microsoft Azure]] automatically received ESUs until July 11, 2023.<ref name=SQL2012ESU(Reminder)>{{cite web\|title=SQL Server 2012 and Windows Server 2012/2012 R2 end of support\|url=https://learn.microsoft.com/lifecycle/announcements/sql-server-2012-windows-server-2012-2012-r2-end-of-support\|archiveurl=https://web.archive.org/web/20220703155353/https://20220703155353/docs.microsoft.com/en-us/lifecycle/announcements/sql-server-2012-windows-server-2012-2012-r2-end-of-support\|date=June 29, 2022\|archivedate=July 3, 2022\|url-status=live}}</ref><ref name=SQL2012ESU(Blog)>{{cite web\|title=Know your options for SQL Server 2012 and Windows Server 2012 End of Support\|first1=Debbi\|last1=Lyons\|first2=Vijay\|last2=Kumar\|url=https://cloudblogs.microsoft.com/sqlserver/2021/07/14/know-your-options-for-sql-server-2012-and-windows-server-2012-end-of-support\|archiveurl=https://web.archive.org/web/20210714150745/https://cloudblogs.microsoft.com/sqlserver/2021/07/14/know-your-options-for-sql-server-2012-and-windows-server-2012-end-of-support\|date=July 14, 2021\|archivedate=July 14, 2021\|url-status=live}}</ref><ref name=SQL2012ESU(Blog2)>{{cite web\|title=Move end-of-support SQL Server 2012 to Azure Virtual Machines and save\|first=Logan\|last=Carrington\|url=https://cloudblogs.microsoft.com/sqlserver/2022/03/24/move-end-of-support-sql-server-2012-to-azure-virtual-machines-and-save\|date=March 24, 2022\|archiveurl=https://web.archive.org/web/20220325031012/https://cloudblogs.microsoft.com/sqlserver/2022/03/24/move-end-of-support-sql-server-2012-to-azure-virtual-machines-and-save\|archivedate=March 25, 2022\|url-status=live}}</ref><ref name=SQL2012ESU(Blog3)>{{cite web\|title= SQL Server 2012 reaches end of support and Microsoft is here to help\|first=Jessica\|last=Hawk\|url=https://cloudblogs.microsoft.com/sqlserver/2022/07/12/sql-server-2012-reaches-end-of-support-and-microsoft-is-here-to-help\|date=July 12, 2022\|archiveurl=https://web.archive.org/web/20220712160411/https://cloudblogs.microsoft.com/sqlserver/2022/07/12/sql-server-2012-reaches-end-of-support-and-microsoft-is-here-to-help\|archivedate=July 12, 2022\|url-status=live}}</ref> ===SQL Server 2008 R2=== SQL Server 2008 R2 (10.50.1600.1, formerly codenamed "Kilimanjaro") was announced at TechEd 2009, and was [[released to manufacturing]] on April 21, 2010.<ref name="SQL Server 2008 R2">{{cite web\|url=http://blogs.technet.com/sqlserverexperts/archive/2010/04/21/sql-server-2008-r2-launches.aspx\|title=SQL Server 2008 R2 Launches!\|accessdate=April 21, 2010}}</ref> SQL Server 2008 R2 introduced several new features and services:<ref name="Networkworld">{{cite web \|date=May 3, 2010 \|title=Review: Microsoft SQL Server 2008 R2 \|url=http://www.networkworld.com/reviews/2010/050310-microsoft-sql-server-2008-test.html?ap1=rcb \|accessdate=June 15, 2013 \|publisher=Networkworld.com}}</ref> * a [[master data management]] system branded as [[Microsoft SQL Server Master Data Services\|Master Data Services]], a central management of master data entities and hierarchies; * a number of services and utilities, collectively known as Application and Multi-Server Management<ref name="Multi-Server Management">{{cite web \|title=SQL SQL Server 2008 R2 Application and Multi-Server Management \|url=http://msdn.microsoft.com/en-us/library/ee364757%28SQL.100%29.aspx \|accessdate=June 6, 2010}}</ref> (AMSM), to manage multiple SQL Server database instances; these utilities included a centralized console named Utility Control Point (UC);<ref name="Innovations">{{cite web\|url=http://blogs.technet.com/dataplatforminsider/archive/2009/05/11/teched-2009-new-sql-server-innovations.aspx\|publisher=MSDN Blogs\|author=SQL Server Team\|accessdate=May 12, 2009\|title=TechEd 2009 – New SQL Server Innovations}}</ref> * [[PowerPivot]] for [[MS Excel\|Excel]] and [[SharePoint]]; * [http://msdn.microsoft.com/en-us/sqlserver/ee476990.aspx StreamInsight]; Line 270: SQL Server 2008 R2 is the last version of SQL Server to run on [[Itanium]] (IA-64) systems, with extended support for SQL Server on Itanium continuing until 2018.<ref>{{cite web\|url=https://rcpmag.com/articles/2010/04/05/microsoft-dropping-itanium-support.aspx\|title=Microsoft Dropping Itanium Support -}}</ref> SQL Server 2008 R2 had mainstream support until July 8, 2014, and extended support until July 9, 2019.<ref>{{cite web\|title=SQL Server 2008 R2 Support Lifecycle\|url=https://learn.microsoft.com/lifecycle/products/microsoft-sql-server-2008-r2\|website=Microsoft Product Lifecycle}}</ref> [[volume licensing\|Volume licensed]] Standard, Enterprise, Datacenter and Embedded editions of SQL Server 2008 R2 are eligible for the Extended Security Updates program.<ref name="ESU4SQL(Doc)" /> The first term of yearly installment ended on July 14, 2020, the second term ended on July 13, 2021, and the third term ended on July 12, 2022.<ref name="SQL2008ESU(Blog)" /><ref name="Products_with_ESU" /> Volume-licensed editions rehosted on [[Microsoft Azure]] automatically received ESUs until July 11, 2023.<ref name="SQL2012ESU(Reminder)" /> ===SQL Server 2012=== Line 277: It was announced to be the last version to natively support [[OLE DB]] and instead to prefer [[ODBC]] for native connectivity.<ref name="ODBC">{{cite web\|title=Microsoft is Aligning with ODBC for Native Relational Data Access — FAQ\|url=http://social.technet.microsoft.com/Forums/en/sqldataaccess/thread/e696d0ac-f8e2-4b19-8a08-7a357d3d780f\|work=SQL Server Forums\|publisher=Microsoft Corporation\|accessdate=March 7, 2012\|last=Lam\|first=Rohan}}</ref> SQL Server 2012's new features and enhancements include Always On SQL Server Failover Cluster Instances and Availability Groups which provides a set of options to improve database availability,<ref name="Availability Enhancements">{{cite web\|url=http://msdn.microsoft.com/en-us/library/cc645581(v=sql.110).aspx\|title=Availability Enhancements (Database Engine)\|date=May 24, 2013 \|publisher=Msdn.microsoft.com\|accessdate=June 15, 2013}}</ref> Contained Databases which simplify the moving of databases between instances, new and modified Dynamic Management Views and Functions,<ref name="Manageability Enhancements">{{cite web\|url=http://msdn.microsoft.com/en-us/library/cc645579(v=sql.110).aspx\|title=Manageability Enhancements (Database Engine)\|publisher=Msdn.microsoft.com\|date=July 13, 2011\|accessdate=June 15, 2013}}</ref> programmability enhancements including new spatial features,<ref name="Aitchison2012">{{cite book\|author=Alastair Aitchison\|title=Pro Spatial with SQL Server 2012\|url=https://books.google.com/books?id=NdvJXu7hT8oC&pg=PA21\|year=2012\|publisher=Apress\|isbn=978-1-4302-3491-3\|pages=21–23}}</ref> metadata discovery, sequence objects and the THROW statement,<ref name="Programmability Enhancements">{{cite web\|url=http://msdn.microsoft.com/en-us/library/cc645577(v=sql.110).aspx\|title=Programmability Enhancements (Database Engine)\|date=April 2012 \|publisher=Msdn.microsoft.com\|accessdate=June 15, 2013}}</ref> performance enhancements such as ColumnStore Indexes as well as improvements to OnLine and partition level operations and security enhancements including provisioning during setup, new permissions, improved role management, and default schema assignment for groups.<ref name="Scalability and Performance Enhancements">{{cite web\|url=http://msdn.microsoft.com/en-us/library/cc645580(v=sql.110).aspx\|title=Scalability and Performance Enhancements (Database Engine)\|date=April 2012 \|publisher=Msdn.microsoft.com\|accessdate=June 15, 2013}}</ref><ref name="Security Enhancements">{{cite web\|url=http://msdn.microsoft.com/en-us/library/cc645578(v=sql.110).aspx\|title=Security Enhancements (Database Engine)\|publisher=Msdn.microsoft.com\|accessdate=June 15, 2013}}</ref> SQL Server 2012 had mainstream support until July 11, 2017, and extended support until July 12, 2022.<ref>{{cite web\|title=SQL Server 2012 Support Lifecycle\|url=https://learn.microsoft.com/lifecycle/products/microsoft-sql-server-2012\|website=Microsoft Product Lifecycle}}</ref><ref name=SQL2012ESU(Reminder)/> All volume licensed editions of SQL Server 2012 are eligible for the Extended Security Updates program.<ref name=ESU4SQL(Doc)/> The first term of yearly installment ended on July 11, 2023, the second term ended on, 2024, and the third and final term ~~will end~~ended on July 8, 2025.<ref name=SQL2012ESU(Blog)/><ref name=Products_with_ESU/> Those volume licensed editions rehosted on [[Microsoft Azure]] automatically ~~receive~~received ESUs until July 8, 2025.<ref name=SQL2012ESU(Blog3)/><ref name=SQL2012ESU(Blog2)/> ===SQL Server 2014=== Line 292: SQL Server 2014 SP1, consisting primarily of bugfixes, was released on May 15, 2015.<ref name="SQL Server 2014 Service Pack 1">{{cite web\|title=SQL Server 2014 Service Pack 1 release information\|url=https://support.microsoft.com/en-us/kb/3058865\|website=Microsoft.com\|publisher=Microsoft, Inc.\|accessdate=May 17, 2015}}</ref> SQL Server 2014 is the last version available for x86/IA-32 systems<ref name="2016 Requirements">{{cite web \|date=May 2, 2016 \|title=Requirements for Installing SQL Server 2016 \|url=https://msdn.microsoft.com/en-us/library/ms143506(v=sql.130).aspx \|accessdate=July 28, 2016 \|publisher=msdn.microsoft.com}}</ref> and the final version supported on [[Windows Server 2008 R2]].<ref>{{Cite web \|date=2017-06-30 \|title=Hardware and Software Requirements for Installing SQL Server 2014 – esiLaw 360 Knowledge Base \|url=https://kb360.esilaw.com/knowledge-base/hardware-and-software-requirements-for-installing-sql-server-2014/ \|access-date=2024-11-10 \|language=en-US}}</ref> SQL Server 2014 had mainstream support until July 9, 2019, and extended support until July 9, 2024.<ref>{{cite web\|title=SQL Server 2014 Support Lifecycle\|url=https://learn.microsoft.com/lifecycle/products/sql-server-2014\|website=Microsoft Product Lifecycle}}</ref> All volume licensed editions of SQL Server 2014 are eligible for the Extended Security Updates program.<ref name=ESU4SQL(Doc)/><ref>{{cite web\|url=https://cloudblogs.microsoft.com/sqlserver/2023/09/28/protect-sql-server-2014-workloads-with-azure-flexibility\|title=Protect SQL Server 2014 workloads with Azure flexibility\|first=Debbi\|last=Lyons\|date=September 28, 2023\|archivedate=October 5, 2023\|archiveurl=https://web.archive.org/web/20231005210526/https://cloudblogs.microsoft.com/sqlserver/2023/09/28/protect-sql-server-2014-workloads-with-azure-flexibility\|website=Microsoft SQL Server Blog\|url-status=live}}</ref> The first term of yearly installment ~~will end~~ended on July 8, 2025, the second term will end on July 14, 2026, and the third and final term will end on July 12, 2027.<ref name=Products_with_ESU/> Those volume licensed editions rehosted on [[Microsoft Azure]] automatically receive ESUs until July 12, 2027. ===SQL Server 2016=== The official General Availability (GA) release date for SQL Server 2016 (13.0.1601.5) was June 1, 2016, with SQL Server 2016 being the first version to only support x64 processors<ref name="2016 Requirements" /> and the last to have the Service Packs updating mechanism. Service Pack 1 was released on November 16, 2016, Service Pack 2 (13.2.5026) was released on April 24, 2018 and Service Pack 3 was released on September 15, 2021. ===SQL Server 2017=== Microsoft launched SQL Server 2017 on October 2, 2017, along with support for [[Linux]].<ref>{{cite web\|url=https://techcrunch.com/2017/07/17/how-microsoft-brought-sql-server-to-linux\|title=How Microsoft brought SQL Server to Linux\|last=Lardinois\|first=Frederic\|date=July 17, 2017\|website=TechCrunch\|publisher=Oath Inc.\|accessdate=September 5, 2017\|quote=The company today launched the first release candidate of SQL Server 2017, which will be the first version to run on Windows, Linux and in Docker containers. The Docker container alone has already seen more than 1 million pulls, so there can be no doubt that there is a lot of interest in this new version.}}</ref><ref>{{Cite web\|url=https://blogs.technet.microsoft.com/dataplatforminsider/2017/10/02/sql-server-2017-on-windows-linux-and-docker-is-now-generally-available/\|title=SQL Server 2017 on Windows Linux and Docker is now generally available\|date=October 2, 2017}}</ref> This is the final release supporting [[Windows Server 2012]] and [[windows Server 2012 R2\|2012 R2]].<ref>{{Cite web \|last=MikeRayMSFT \|date=2024-09-16 \|title=SQL Server 2016 & 2017: Hardware & software requirements - SQL Server \|url=https://learn.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server?view=sql-server-ver16#operating-system-support-for-sql-server-2017 \|access-date=2024-11-10 \|website=learn.microsoft.com \|language=en-us}}</ref><ref>{{Cite web \|last=MikeRayMSFT \|date=2024-09-17 \|title=SQL Server 2019: Hardware & software requirements - SQL Server \|url=https://learn.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2019?view=sql-server-ver16 \|access-date=2024-11-10 \|website=learn.microsoft.com \|language=en-us}}</ref> ===SQL Server 2019=== Microsoft launched SQL Server 2019 (15.x) on November 4, 2019. SQL Server 2019 introduces Big Data Clusters for SQL Server. It also provides additional capability and improvements for the SQL Server database engine, SQL Server Analysis Services, SQL Server Machine Learning Services, SQL Server on Linux, and SQL Server Master Data Services.<ref>{{cite web\|title=What's new in SQL Server 2019 (15.x)\| date=March 16, 2023 \|url=https://docs.microsoft.com/en-us/sql/sql-server/what-s-new-in-sql-server-ver15?view=sql-server-ver15}}</ref> ===SQL Server 2022=== Line 506: \|{{no}} \|{{no}} \|{{yes}} (Edge)<ref>{{Cite web\|url=https://docs.microsoft.com/en-us/azure/azure-sql-edge/deploy-portal\|title=Deploy Azure SQL Edge using the Azure portal\|date=January 15, 2023 }}</ref> \|{{no}} \|- Line 531: [[Category:Relational database management systems]] [[Category:Windows Server System\|SQL Server]] [[Category:Software topical history overviews\|Microsoft SQL Server]] [[Category:Software version histories\|Microsoft SQL Server]]