Content deleted Content added
m →SQL Server 2014: Move bracket |
|||
| (23 intermediate revisions by 13 users not shown) | |||
Line 6:
==Versions==
<!--Template:Version - for version & release history. Documentation and examples: http://en.wikipedia.org/wiki/Template:Version-->
{|style=text-
|-
!Version
Line 52:
|{{dunno}}
|{{dunno}}
|SQL Server
|SQLNT
|{{dash}}
Line 155:
|June 5, 2014
|{{version|o|July 9, 2019}}
|{{version|
|SQL Server 2014
|Hekaton
Line 178:
|15.0
|November 4, 2019
|{{version|
|{{version|co|January 8, 2030}}
|SQL Server 2019
Line 198:
==Detailed history==
===Genesis===
By 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}}
On June 12, 1988, Microsoft joined [[Ashton-Tate]] and [[Sybase]] to create a variant of [[Sybase SQL Server]] for [[IBM]] [[OS/2]] (then developed jointly with Microsoft), which was released the following year.<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 database|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.▼
▲
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.▼
▲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.
===SQL Server 2000===
SQL Server 2000 included more modifications and extensions to the Sybase code base, adding support for the [[IA-64]] architecture (now out of "mainstream" support<ref>{{cite web|url=http://www.computerworld.com/article/2516742/computer-hardware/microsoft-ending-support-for-itanium.html|title=Microsoft ending support for Itanium|date=April 4, 2010}}</ref>). By SQL Server 2005 the legacy Sybase code had been completely rewritten.<ref name="Scriptcase">{{cite web|url=http://www.scriptcase.net/blog/all-about-the-history-of-sql-server/|title=All about the History of SQL Server|website=Scriptcase.net.|date=August 14, 2013|accessdate=August 15, 2016|archive-date=September 16, 2016|archive-url=https://web.archive.org/web/20160916133043/http://www.scriptcase.net/blog/all-about-the-history-of-sql-server/|url-status=dead}}</ref>
Since the release of SQL Server 2000, advances have been made in performance, the client IDE tools, and several complementary systems that are packaged with SQL Server 2005. These include:
Line 224 ⟶ 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
[[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>
SQL Server 2005 introduced:
SQL Server 2005 introduced [[Multiversion concurrency control|Multi-Version Concurrency Control]] (MVCC). User facing features include new transaction isolation level called SNAPSHOT and a variation of the READ COMMITTED isolation level based on statement-level data snapshots.▼
SQL Server 2005 introduced "MARS" (Multiple Active Results Sets), a method of allowing usage of [[database connection]]s for multiple purposes.<ref name="MARS">[http://msdn.microsoft.com/en-us/library/ms345109(SQL.90).aspx Multiple Active Result Sets (MARS) in SQL Server 2005. retrieved June 20, 2009]</ref>▼
SQL Server 2005 introduced DMVs (Dynamic Management Views), which are 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) of SQL Server 2005 introduced Database Mirroring, a high availability option that provides redundancy and failover capabilities at the database level.<ref name="database mirroring">{{cite web|url=http://support.microsoft.com/kb/907741|title=Issues to consider when you use the database mirroring feature in the initial release of SQL Server 2005|publisher=Support.microsoft.com|date=November 20, 2007|accessdate=September 4, 2011}}</ref> Failover can be performed manually or can be configured for automatic failover. 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|url=http://msdn.microsoft.com/en-us/library/ms189590.aspx|title=Automatic Failover|publisher=Msdn.microsoft.com|accessdate=September 4, 2011}}</ref> Database Mirroring was included in the first release of SQL Server 2005 for evaluation purposes only. Prior to SP1, it was not enabled by default, and was not supported by Microsoft.{{citation needed|date=June 2015}}▼
▲
▲
▲Service Pack 1 (SP1)
Mainstream support for SQL Server 2005 ended on April 12, 2011, and Extended support for SQL Server 2005 ended on April 12, 2016.
Line 247 ⟶ 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
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 255 ⟶ 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 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
Also Multi Server Management, a centralized console to manage multiple SQL Server 2008 instances and services including relational databases, Reporting Services, Analysis Services & Integration Services.<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>▼
* 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;
▲
* [[PowerPivot]] for [[MS Excel|Excel]] and [[SharePoint]];
* [http://msdn.microsoft.com/en-us/sqlserver/ee476990.aspx StreamInsight];
* [[Report Builder]] 3.0 and [https://technet.microsoft.com/en-us/sqlserver/ff660783.aspx Reporting Services] Add-in for SharePoint;
* a Data-tier function in Visual Studio that enables packaging of tiered databases as part of an application.
SQL Server 2008 R2
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"/>
===SQL Server 2012===
At the 2011
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
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
===SQL Server 2014===
Line 289 ⟶ 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
▲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 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
===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
===SQL Server 2022===
Line 317 ⟶ 312:
|+Processor support for SQL Server
!Version
![[Intel 80286|
![[IA-32
![[x86-64|x64]]
![[DEC Alpha]]
Line 324 ⟶ 319:
![[PowerPC]]
![[IA-64|Itanium]]
![[ARM architecture family|ARM]]
![[SuperH|SH4]]
|-
Line 503 ⟶ 498:
|{{no}}
|-
|SQL 2019
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{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
|{{no}}
|-
|SQL 2022+
|{{no}}
|{{no}}
Line 511 ⟶ 517:
|{{no}}
|{{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 525 ⟶ 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]]
| |||