Hubbry Logo
History of Microsoft SQL ServerHistory of Microsoft SQL ServerMain
Open search
History of Microsoft SQL Server
Community hub
History of Microsoft SQL Server
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
History of Microsoft SQL Server
History of Microsoft SQL Server
History of Microsoft SQL Server
View on Wikipedia
from Wikipedia

The history of Microsoft SQL Server begins with the first Microsoft SQL Server database product – SQL Server v1.0, a 16-bit relational database for the OS/2 operating system, released in 1989.

Versions

[edit]
Version Release
Date 		Mainstream
End Date 		Extended
End Date 		Release name Code name Internal
database version
1.0 (OS/2) 1989 ? ? SQL Server 1.0 (16-bit) Filipi  –
1.1 (OS/2) 1990 ? ? SQL Server 1.1 (16-bit) Pietro  –
4.2A (OS/2) 1992 ? ? SQL Server 4.2A  –  –
4.2B (OS/2) 1993 ? ? SQL Server 4.2B (16-bit)  –  –
4.21a (WinNT) 1993 ? ? SQL Server 1a SQLNT  –
6.0 1995 ? ? SQL Server 6.0 SQL95 406
6.5 1996 ? ? SQL Server 6.5 Hydra 408
7.0 1998 Unsupported: December 31, 2005 Unsupported: January 11, 2011 SQL Server 7.0 Sphinx 515
— 1999 ? ? SQL Server 7.0 OLAP Tools Plato  –
8.0 2000 Unsupported: April 8, 2008 Unsupported: April 9, 2013 SQL Server 2000 Shiloh 539
8.0 2003 ? ? SQL Server 2000 64-bit Edition Liberty 539
9.0 January 14, 2006 Unsupported: April 12, 2011 Unsupported: April 12, 2016 SQL Server 2005 Yukon 611/612
10.0 November 6, 2008 Unsupported: July 8, 2014 Unsupported: July 9, 2019 SQL Server 2008 Katmai 655
10.25 2010 ? ? Azure SQL database (initial release) Cloud database or CloudDB  –
10.50 July 20, 2010 Unsupported: July 8, 2014 Unsupported: July 9, 2019 SQL Server 2008 R2 Kilimanjaro (aka KJ) 661
11.0 May 20, 2012 Unsupported: July 11, 2017 Unsupported: July 12, 2022 SQL Server 2012 Denali 706
12.0 2014 ? ? Azure SQL database  –  –
12.0 June 5, 2014 Unsupported: July 9, 2019 Unsupported: July 9, 2024 SQL Server 2014 Hekaton 782
13.0 June 1, 2016 Unsupported: July 13, 2021 Supported: July 14, 2026 SQL Server 2016 SQL16 852
14.0 September 29, 2017 Unsupported: October 11, 2022 Supported: October 12, 2027 SQL Server 2017 Helsinki 869
15.0 November 4, 2019 Unsupported: January 14, 2025 Supported: January 8, 2030 SQL Server 2019 Seattle 895
16.0 November 16, 2022 Latest version: January 11, 2028 Latest version: January 11, 2033 SQL Server 2022 Dallas 957
Legend:   Old version   Older version, still maintained   Latest version

Detailed history

[edit]

Genesis

[edit]

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,[1] 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.[2]

Scheduled for the second half of 1988,[2] it was released in 1989.[3] 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.[1] 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

[edit]
SQL Server 7.0 Splash Screen

After problems at its main rivals, SQL Server became Oracle's most important competitor.[4] 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[5]). 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

[edit]

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[6]). By SQL Server 2005 the legacy Sybase code had been completely rewritten.[7]

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:

SQL Server 2000 also introduced many T-SQL language enhancements, such as table variables, user-defined functions, indexed views, INSTEAD OF triggers, cascading referential constraints and some basic XML support.[8][9]

With the release of Service Pack 3, Microsoft also released the first 64-bit version of the SQL Server for the Itanium IA-64 platform (not to be confused with the x86-64 platform). Only the SQL Server relational engine and SQL Agent were ported to Itanium at this time. Client tools, such as SQL Server Management Studio, were still 32-bit x86 programs. The first release of SQL IA-64 was version 8.00.760, with a build date of February 6, 2003.

Mainstream support ended on April 8, 2008, and extended support ended on April 9, 2013.

SQL Server 2005

[edit]

SQL Server 2005 (formerly codenamed "Yukon") was released in November 2005, introducing native support for x64 systems and updates to Reporting Services, Analysis Services & Integration Services.[10] It included native support for managing XML data, in addition to relational data. For this purpose, it defined an xml data type that could be used either as a data type in database columns or as literals 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 services using Tabular Data Stream (TDS) packets encapsulated within SOAP requests. When the data is accessed over web services, results are returned as XML.[11]

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 checksummed 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 is easier. SQL CLR was introduced with SQL Server 2005 to let it integrate with the .NET Framework.[12]

SQL Server 2005 introduced:

  • 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.
  • Multiple Active Results Sets (MARS), a method of allowing usage of database connections for multiple purposes.[13]
  • 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.[14]

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[15] (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]). 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).[16] 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.

SQL Server 2008

[edit]

SQL Server 2008 (formerly codenamed "Katmai")[17][18] was released on August 6, 2008, announced to the SQL Server Special Interest Group at the ESRI 2008 User's Conference on August 6, 2008, by Ed Katibah (Spatial Program Manager at Microsoft), and aims to make data management self-tuning, self organizing, and self maintaining with the development of SQL Server Always On technologies, to provide near-zero downtime. SQL Server 2008 also includes support for structured and semi-structured data, including digital media formats for pictures, audio, video and other multimedia data. In current versions, such multimedia data can be stored as BLOBs (binary large objects), but they are generic bitstreams. Intrinsic awareness of multimedia data will allow specialized functions to be performed on them. According to Paul Flessner, senior Vice President of Server Applications at Microsoft, SQL Server 2008 can be a data storage backend for different varieties of data: XML, email, time/calendar, file, document, spatial, etc. as well as perform search, query, analysis, sharing, and synchronization across all data types.[18]

Other new data types include specialized date and time types and a Spatial data type for location-dependent data.[19] Better support for unstructured and semi-structured data is provided using the new FILESTREAM[20] data type, which can be used to reference any file stored on the file system.[21] 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 APIs 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.[22] SQL Server 2008 also natively supports hierarchical data, and includes T-SQL constructs to directly deal with them, without using recursive queries.[22]

The full-text search functionality has been integrated with the database engine. According to a Microsoft technical article, this simplifies management and improves performance.[23]

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.[24]

SQL Server includes better compression features, which also helps in improving scalability.[25] It enhanced the indexing algorithms and introduced the notion of filtered indexes. It also includes Resource Governor that allows reserving resources for certain users or workflows. It also includes capabilities for transparent encryption of data (TDE) as well as compression of backups.[20] SQL Server 2008 supports the ADO.NET Entity Framework and the reporting tools, replication, and data definition will be built around the Entity Data Model.[26] SQL Server Reporting Services will gain charting capabilities from the integration of the data visualization products from Dundas Data Visualization, Inc., which was acquired by Microsoft.[27] On the management side, SQL Server 2008 includes the Declarative Management Framework which allows configuring policies and constraints, on the entire database or certain tables, declaratively.[19] The version of SQL Server Management Studio included with SQL Server 2008 supports IntelliSense for SQL queries against a SQL Server 2008 Database Engine.[28] SQL Server 2008 also makes the databases available via Windows PowerShell providers and management functionality available as Cmdlets, so that the server and all the running instances can be managed from Windows PowerShell.[29]

The final SQL Server 2008 service pack (10.00.6000, Service Pack 4) was released on September 30, 2014.[30]

SQL Server 2008 had mainstream support until July 8, 2014, and extended support until July 9, 2019.[31] Volume licensed Standard, Web, Enterprise, Workgroup and Datacenter editions of SQL Server 2008 are eligible for the Extended Security Updates program.[32] 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.[33][34] Those volume licensed editions rehosted on Microsoft Azure automatically received ESUs until July 11, 2023.[35][36][37][38]

SQL Server 2008 R2

[edit]

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.[39] SQL Server 2008 R2 introduced several new features and services:[40]

Service Pack 1 (10.50.2500) was released on July 11, 2011,[43] Service Pack 2 (10.50.4000) was released on July 26, 2012[44] and the final service pack, Service Pack 3 (10.50.6000), was released on September 26, 2014.[45]

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.[46]

SQL Server 2008 R2 had mainstream support until July 8, 2014, and extended support until July 9, 2019.[47] Volume licensed Standard, Enterprise, Datacenter and Embedded editions of SQL Server 2008 R2 are eligible for the Extended Security Updates program.[32] 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.[33][34] Volume-licensed editions rehosted on Microsoft Azure automatically received ESUs until July 11, 2023.[35]

SQL Server 2012

[edit]

At the 2011 Professional Association for SQL Server (PASS) summit on October 11, Microsoft announced another major version of SQL Server, SQL Server 2012 (codenamed "Denali"). The final version was released to manufacturing on March 6, 2012.[48] SQL Server 2012 Service Pack 1 was released to manufacturing on November 7, 2012, Service Pack 2 was released to manufacturing on June 10, 2014, Service Pack 3 was released to manufacturing on December 1, 2015, and Service Pack 4 was released to manufacturing on October 5, 2017.

It was announced to be the last version to natively support OLE DB and instead to prefer ODBC for native connectivity.[49]

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,[50] Contained Databases which simplify the moving of databases between instances, new and modified Dynamic Management Views and Functions,[51] programmability enhancements including new spatial features,[52] metadata discovery, sequence objects and the THROW statement,[53] 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.[54][55]

SQL Server 2012 had mainstream support until July 11, 2017, and extended support until July 12, 2022.[56][35] All volume licensed editions of SQL Server 2012 are eligible for the Extended Security Updates program.[32] The first term of yearly installment ended on July 11, 2023, the second term ended on, 2024, and the third and final term ended on July 8, 2025.[36][34] Those volume licensed editions rehosted on Microsoft Azure automatically received ESUs until July 8, 2025.[38][37]

SQL Server 2014

[edit]

SQL Server 2014 was released to manufacturing on March 18, 2014, and released to the general public on April 1, 2014, and the build number was 12.0.2000.8 at release.[57] Until November 2013 there were two CTP revisions, CTP1 and CTP2.[58] SQL Server 2014 provides a new in-memory capability for tables that can fit entirely in memory (also known as Hekaton). Whilst small tables may be entirely resident in memory in all versions of SQL Server, they also may reside on disk, so work is involved in reserving RAM, writing evicted pages to disk, loading new pages from disk, locking the pages in RAM while they are being operated on, and many other tasks. By treating a table as guaranteed to be entirely resident in memory much of the 'plumbing' of disk-based databases can be avoided.[59]

For disk-based SQL Server applications, it also provides the SSD Buffer Pool Extension, which can improve performance by cache between RAM and spinning media.

SQL Server 2014 also enhances the Always On (HADR) solution by increasing the readable secondaries count and sustaining read operations upon secondary-primary disconnections, and it provides new hybrid disaster recovery and backup solutions with Microsoft Azure, enabling customers to use existing skills with the on-premises version of SQL Server to take advantage of Microsoft's global datacenters. In addition, it takes advantage of new Windows Server 2012 and Windows Server 2012 R2 capabilities for database application scalability in a physical or virtual environment.

Microsoft provides three versions of SQL Server 2014 for downloading: the one that runs on Microsoft Azure, the SQL Server 2014 CAB, and SQL Server 2014 ISO.[60]

SQL Server 2014 SP1, consisting primarily of bugfixes, was released on May 15, 2015.[61]

SQL Server 2014 is the last version available for x86/IA-32 systems[62] and the final version supported on Windows Server 2008 R2.[63]

SQL Server 2014 had mainstream support until July 9, 2019, and extended support until July 9, 2024.[64] All volume licensed editions of SQL Server 2014 are eligible for the Extended Security Updates program.[32][65] The first term of yearly installment 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.[34] Those volume licensed editions rehosted on Microsoft Azure automatically receive ESUs until July 12, 2027.

SQL Server 2016

[edit]

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[62] 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

[edit]

Microsoft launched SQL Server 2017 on October 2, 2017, along with support for Linux.[66][67] This is the final release supporting Windows Server 2012 and 2012 R2.[68][69]

SQL Server 2019

[edit]

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.[70]

SQL Server 2022

[edit]

Microsoft launched SQL Server 2022 on November 16, 2022.[71][unreliable source?] However, customers purchasing via OEM, and Services Provider License Agreement (SPLA) had to purchase SQL Server 2022 starting January 2023.[72]

Processor support

[edit]
Processor support for SQL Server
Version Intel 286 IA-32 x64 DEC Alpha MIPS PowerPC Itanium ARM SH4
SQL 1.0 Yes Yes No No No No No No No
SQL 1.1 Yes Yes No No No No No No No
SQL 4.2 Yes Yes No No No No No No No
SQL 4.21 No Yes No Yes Yes No No No No
SQL 6.0 No Yes No Yes Yes No No No No
SQL 6.5 No Yes No Yes Yes Ends after SP2 No No No
SQL 7.0 No Yes No Yes No No No No No
SQL 2000 No Yes No Pre-release only No No Starts at SP3 No No
SQL 2000 CE No Yes Yes No Yes No No Yes Yes
SQL 2005 No Yes Yes No No No Yes No No
SQL 2005 CE No Yes Yes No Yes No No Yes Yes
SQL 2008 No Yes Yes No No No Yes No No
SQL 2008 R2 No Yes Yes No No No Yes No No
SQL 2012 No Yes Yes No No No No No No
SQL 2014 No Yes Yes No No No No No No
SQL 2016/17 No No Yes No No No No No No
SQL 2019 No No Yes No No No No Yes (Edge)[73] No
SQL 2022+ No No Yes No No No No No No

References

[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

History of Microsoft SQL Server

View on Grokipedia
from Grokipedia
The history of Microsoft SQL Server documents the development of this proprietary (RDBMS) from its origins as a collaborative project to its role as a mature enterprise platform supporting , processing, and analytics across on-premises, cloud, and hybrid environments. Initially released in 1989 as a 16-bit server for the operating system, SQL Server was built on Sybase's SQL Server code under a partnership between , Sybase, and , providing Microsoft with its first foothold in the RDBMS market. Over more than three decades, the product has seen iterative enhancements in scalability, security, performance, and integration with emerging technologies like and tools, evolving into a cornerstone of Microsoft's . The early years of SQL Server were defined by its joint development with Sybase, which supplied the core relational engine and query language that remain foundational today. By 1993, the partnership concluded, allowing to independently adapt the technology for with the release of SQL Server 4.21, the first version optimized for that platform. This shift enabled rapid innovation; SQL Server 6.0 arrived in 1995, introducing improved and distributed queries, while SQL Server 7.0 in 1998 leveraged the Windows NT kernel for better integration, adding features like . SQL Server 2000, released in 2000, further expanded capabilities with native XML support, analysis services for OLAP, and replication for , solidifying its position against competitors like . Entering the 2000s, SQL Server aligned closely with Microsoft's .NET strategy, with SQL Server 2005 introducing (CLR) integration for stored procedures in managed code and enhanced features. Subsequent releases built on this foundation: SQL Server 2008 added self-tuning capabilities, while SQL Server 2008 R2 in 2010 enhanced tools. By SQL Server 2012, performance optimizations like columnstore indexes were prioritized, and later versions such as SQL Server 2014 and 2016 incorporated in-memory OLTP for faster transaction processing. In recent years, SQL Server has embraced cross-platform deployment and cloud-native features to meet modern demands. SQL Server 2017 marked the product's support for and Docker containers, broadening its accessibility beyond Windows. SQL Server 2019 advanced integration with and HDFS support in Big Data Clusters, alongside improvements in intelligent query processing. SQL Server 2022 introduced Azure Link for real-time analytics and enhanced security with ledger tables for tamper-proof data; SQL Server 2025, released in November 2025, introduces consolidation of on-premises reporting services under Power BI Report Server. Throughout its history, regular updates and service packs have addressed security vulnerabilities and performance issues, ensuring long-term support for enterprise users.

Early Development

Origins and Sybase Partnership

In January 1988, Microsoft Corporation announced a joint development agreement with Sybase, Inc., and Ashton-Tate Corporation to create a relational database management system (RDBMS) for Microsoft's OS/2 operating system. Under the terms, Sybase licensed its existing relational database server technology—originally developed for UNIX platforms—to Microsoft for adaptation to local area networks (LANs) on OS/2, while Ashton-Tate handled integration with its popular dBASE product to enable seamless data access for existing applications. This collaboration aimed to deliver a robust, multi-user database solution optimized for PC-based client-server environments, building on Sybase's core SQL engine to support industry-standard Structured Query Language (SQL) queries. The partnership focused on porting and enhancing Sybase's Data Server for , emphasizing management capabilities such as , , and networked access for workgroup computing. By leveraging Sybase's proven SQL engine, the project avoided building a database from scratch, allowing to quickly enter the enterprise database market with a product that supported stored procedures, triggers, and basic indexing. Ashton-Tate's role extended to retail distribution through its channels, while Sybase handled corporate sales of the integrated package, ensuring broad market reach for users transitioning to client-server architectures. Microsoft SQL Server 1.0 was first shipped in April 1989 as an add-on product for OS/2 1.2, marking the first commercial version of the jointly developed RDBMS. It was priced at a suggested retail of $2,495 per server installation, with no per-user limits, though upgrades from developer kits were available for $300. Key technical specifications included support for processors, compatibility with OS/2's memory model up to 16 MB of RAM, and the introduction of a basic (T-SQL) dialect—an extension of ANSI SQL tailored for procedural extensions like control-of-flow language. The product required approximately 10 MB of RAM for smooth operation and 30 MB of disk space, reflecting the era's hardware constraints for 16-bit server applications. From the outset, SQL Server 1.0 was marketed as an affordable, open client-server RDBMS for LANs, directly targeting competition with established players like by offering scalable multi-user access for DOS, , and early Windows clients over networks such as 3+Open and LAN Server. This positioning emphasized its role in enabling networked, relational data management for business applications without the high costs of mainframe or proprietary systems.

Initial Releases (1989–1995)

The initial releases of Microsoft SQL Server marked Microsoft's entry into the relational database market through a partnership with Sybase, which provided the core codebase, and , which contributed to marketing and front-end integration efforts for the 1.0 version. Released in 1989 as a 16-bit server for , SQL Server 1.0 offered basic networking support and the System Administrator Facility (SAF) for database creation and queries, targeting departmental LAN environments. In 1991, SQL Server 1.1 (codenamed Pietro) extended platform compatibility by adding support for 1.3 and a preview release of , enabling early testing on Microsoft's emerging enterprise operating system while maintaining compatibility. This version also coincided with the end of Ashton-Tate's direct involvement following its acquisition by in 1991, as the partnership shifted focus away from integration toward broader Windows adoption. In 1993, SQL Server 4.21 (codenamed SQLNT) achieved full production support for alongside 1.3, introducing enhancements to stored procedures for reusable code execution, triggers for automated event-based actions, and views for simplified data abstraction, which improved developer productivity and . The 1993 release of SQL Server 4.21 further expanded hardware compatibility by adding support for the architecture, aiming to leverage RISC processors for better performance in non-x86 environments, though adoption remained limited due to optimization challenges and the x86-centric Windows ecosystem. SQL Server 6.0, released in 1995 (codenamed SQL95), represented a major incremental update with tight integration to , introducing for efficient querying of and replication features including snapshot, transactional, and merge types to support distributed database . These enhancements boosted for mid-sized enterprises, yet SQL Server faced stiff market challenges from 's established dominance in high-end relational databases, where Oracle held superior in the through its Unix-based and enterprise features, while SQL Server struggled with perceptions of limited robustness on non-x86 platforms.

Transition to Independence

Departure from Sybase

In 1994, Microsoft and Sybase formally ended their joint development partnership for SQL Server, marking a pivotal shift in the product's evolution. The announcement came on April 12, 1994, with each company agreeing to pursue independent development paths. Microsoft acquired full ownership and rights to the Windows-based versions of SQL Server, allowing it to tailor the database exclusively for its operating systems, while Sybase retained control over the Unix versions, which would later be rebranded as Adaptive Server Enterprise (ASE). This separation stemmed from diverging strategic priorities, as Microsoft's growing emphasis on Windows NT clashed with Sybase's focus on cross-platform portability. The agreement had immediate implications for ongoing product work, particularly SQL Server 6.0, released in June 1995 as the last major version developed collaboratively. Although the split occurred mid-development, Microsoft assumed complete responsibility for Windows and Intel x86 platform enhancements, enabling it to optimize the release for NT environments without Sybase's input on those fronts. Sybase continued to receive royalties from Microsoft's Windows sales during a transitional period, but the partnership's dissolution allowed both firms to eliminate overlapping efforts and reduce royalty dependencies that had previously tied their revenues—Sybase earned approximately $20 million in 1993 from a 5% royalty on Microsoft SQL Server sales. This transition ensured continuity for existing customers while setting the stage for divergent architectures. Internally, the departure prompted Microsoft to restructure its database engineering efforts, establishing a more autonomous SQL Server development group to accelerate innovation tailored to Windows ecosystems. This reorganization emphasized building deeper integrations with Windows NT features, such as native threading and memory management, to position SQL Server as a superior choice for Windows-centric enterprises. By prioritizing this tight OS coupling, Microsoft aimed to differentiate its product from cross-platform rivals like and Sybase's Unix offerings, leveraging Windows' expanding market share to drive adoption among business users. The strategic pivot not only resolved tensions from the but also fueled Microsoft's long-term dominance in the relational database market.

SQL Server 6.0 and 6.5

SQL Server 6.0, released in June 1995, marked a significant evolution in Microsoft's database offerings following the end of the Sybase partnership, with the product now fully under Microsoft's control. This version introduced enhanced security measures, including improved user authentication and access controls, to better protect enterprise data environments. It also added support for distributed queries, enabling seamless integration and querying across multiple data sources, which laid groundwork for more complex heterogeneous environments. Additionally, SQL Server 6.0 served as a precursor to OLAP services by incorporating support capabilities that facilitated analytical processing on large datasets. Building on 6.0, SQL Server 6.5 was released to manufacturing in April 1996 and became generally available in June 1996, focusing on stability and enterprise readiness as the final pre-rewrite iteration. A key addition was clustering support through integration with Compaq's Recovery Server, providing automatic for in mission-critical scenarios. Performance tuning tools were enhanced with features like dynamic locking, which automatically adjusted lock granularity (from row to database level) to balance concurrency and throughput, and native threading for improved parallelism. This release was also the last to support the MIPS architecture, catering to diverse hardware platforms including x86, , and Motorola . Both versions emphasized bug fixes and scalability improvements to address growing enterprise demands. SQL Server 6.0 and 6.5 supported databases up to 32 GB in size, a substantial increase from prior limits, enabling handling of larger workloads without frequent partitioning. Backup and restore processes were refined for greater reliability, with 6.5 introducing the ability to back up and restore individual tables alongside options via transaction logs, reducing downtime during maintenance. These enhancements included heterogeneous replication to databases like , , and Sybase, as well as coordination for atomic multiserver operations. Mainstream support for SQL Server 6.0 ended in 2000, while extended support for concluded on January 1, 2002, after which no further updates or security patches were provided. User feedback during this era highlighted issues with inherited from the Sybase codebase, including inefficient legacy structures that hampered performance and maintenance, ultimately influencing the decision for a ground-up rewrite in the next major version.

Rewrite and Core Modernization

Development of SQL Server 7.0

Following the experiences with SQL Server 6.5, which highlighted limitations in scalability and granular locking for high-concurrency environments, Microsoft launched a comprehensive to create a fully independent, Windows-native . This initiative, spanning from approximately 1995 to 1998, aimed to transform SQL Server into a high-performance system optimized for the Windows platform, moving away from the shared Sybase that had constrained prior . Codenamed Sphinx internally, the focused on building a componentized architecture that would enable better , allowing individual components like storage and query processing to be developed and optimized independently. The development effort involved a dedicated team of engineers led by key architects including David Vaskevitch, Peter Spiro, and Phil Bernstein, with contributions from researchers like Jim Gray to inform core design decisions. Emphasis was placed on creating a scalable capable of handling terabyte-scale warehousing and enterprise workloads, with planned innovations such as a new cost-based query optimizer incorporating heuristics for faster plan generation and reduced compilation times. Another major goal was advancing toward zero-administration capabilities through auto-configuration and auto-tuning features, intended to minimize manual intervention in setup, maintenance, and for administrators. These objectives aligned with Microsoft's broader vision for lower , targeting both small-scale mobile deployments and large multi-processor servers. The project also introduced (DTS), an extract-transform-load (ETL) tool for data integration tasks. Beta testing commenced in June 1997, with previews demonstrating substantial performance improvements over SQL Server 6.5; for instance, early benchmarks showed up to 10x gains in scalability for enterprise applications like Baan, alongside doubled throughput in workloads. By mid-1998, Beta 3 had reached over 100,000 production sites, providing extensive feedback that refined the engine's reliability and integration points. During this phase, the team incorporated preview features from the upcoming , such as enhanced security protocols compatible with , to ensure seamless interoperability and authentication in enterprise environments. This forward-looking integration helped position SQL Server as a cornerstone of Microsoft's enterprise ecosystem, even before Windows 2000's release.

SQL Server 7.0

SQL Server 7.0, codenamed , was released to general availability in November 1998 after a delay from its originally planned earlier launch. This version represented Microsoft's first fully independent SQL Server release following the separation from , building on an extensive rewrite of the underlying codebase to enhance performance and scalability. The product marked a pivotal shift, introducing a completely new storage engine that supported row-level locking, improved concurrency, and more efficient logging and recovery mechanisms compared to prior versions. Key innovations in SQL Server 7.0 included the Index Tuning Wizard, a tool designed to analyze workloads and recommend optimal index configurations to boost query performance without manual intervention. Additionally, it integrated English Query, a interface that allowed users to submit database queries in everyday English sentences, translating them into SQL for execution. These features, combined with automated maintenance tasks like statistics updates and index reorganization, significantly simplified database administration and appealed to a broader range of users beyond expert DBAs. The rewrite process, which involved converting the code from C to C++ and redesigning core components, laid the foundation for these advancements, including enhanced capabilities. SQL Server 7.0 was offered in three main editions: Standard for general-purpose use, Enterprise for high-volume transactional workloads with advanced scalability options, and Personal (also known as Desktop Edition) targeted at developers and small-scale applications. Pricing began at approximately $699 for the Personal Edition under promotional offers, making it more accessible for entry-level deployments while Enterprise editions commanded higher costs for robust features like clustering support. This edition lineup helped democratize access to enterprise-grade database technology. The release was the last to support the architecture, reflecting Microsoft's focus on x86 platforms amid shifting hardware trends. Mainstream support ended on December 31, 2005, with extended support concluding on January 11, 2011. In terms of market reception, SQL Server 7.0 propelled to approximately 35% of the market share on the Windows platform by 2000, lauded particularly for its ease of use and cost-effectiveness in Windows environments, which facilitated rapid adoption among mid-sized businesses and developers.

SQL Server 2000

Microsoft SQL Server 2000, codenamed Shiloh, reached release to manufacturing (RTM) on August 7, 2000, marking a significant in Microsoft's database platform with a focus on enhanced scalability, web integration, and enterprise-level capabilities. This version built upon the architectural foundations of SQL Server 7.0 while introducing features tailored for and data-intensive applications, supporting up to 32 processors and 64 GB of RAM in its Enterprise Edition to handle growing business demands. General availability followed on November 30, 2000, with Microsoft emphasizing its tight integration with for improved reliability and performance in distributed environments. A key advancement in SQL Server 2000 was its native XML support, including XML views that allowed relational data to be queried and returned directly as XML documents over HTTP, streamlining web-centric application development without requiring custom . This feature enabled developers to expose database content via URLs, facilitating easier integration with emerging web technologies and positioning SQL Server as a robust backend for XML-driven services. Complementing this, Analysis Services 2000 provided advanced OLAP functionality, supporting multidimensional through cubes, dimensions, and measures that enabled complex aggregations and slicing for tasks. Additionally, English Query 3.0 allowed end-users to interact with the database using questions, translating English phrases into SQL queries to broaden accessibility for non-technical users. The Enterprise Edition supported the IA-64 () architecture from its initial release, enabling 64-bit processing for larger memory addressing and improved performance on enterprise servers. Editions were expanded to include the Developer Edition, which offered full Enterprise Edition features free of charge for non-production use, such as development and testing, to encourage broader adoption among developers. SQL Server 2000 also previewed integration with the .NET Framework through enhanced XML capabilities and data access components, laying groundwork for future managed code interoperability in web and application development, and included a preview of Notification Services for event-driven applications. Mainstream support ended on April 8, 2008, with extended support concluding on April 9, 2013.

Enterprise and Integration Advances

SQL Server 2005

SQL Server 2005, codenamed , was released on November 7, 2005, following delays from its originally planned 2004 launch due to the extensive scope of its architectural changes. This version marked a significant evolution in Microsoft's database platform, emphasizing deeper integration with .NET Framework technologies and support for emerging hardware architectures, which enabled more robust enterprise applications and improved . A major innovation was the integration of the (CLR) directly into the database engine, allowing developers to write stored procedures, functions, triggers, and user-defined types in managed languages such as C# or VB.NET. This CLR support extended SQL Server's programmability beyond T-SQL, facilitating complex computations and custom logic within the database while maintaining security through code access security and permission sets. Complementing this, the introduction of the native XML data type provided built-in storage and querying for XML documents, building briefly on the XML enhancements from SQL Server 2000 by adding validation against XML schemas, indexing, and methods like .query() for operations. Additionally, Service Broker emerged as a reliable asynchronous messaging framework for building database-integrated applications, supporting queued operations and conversations without external . SQL Server 2005 introduced native support for 64-bit (x64 and ) architectures, allowing the to fully leverage larger memory capacities and multi-core processors for better performance in data-intensive workloads. Notification Services was another key addition, enabling the creation of event-driven alert systems that monitor data changes and deliver notifications via , , or other protocols, which proved useful for real-time applications like dashboards. The release expanded edition options to cater to diverse needs, including the free SQL Server 2005 Express Edition, a lightweight version limited to 1 GB of memory and 4 GB databases but suitable for development and small-scale deployments. Security was bolstered with features like stricter default configurations—such as disabling ad-hoc remote queries and sa account—and in Express Edition, user instances that provided isolated, per-user database environments to prevent interference and enhance data protection. Mainstream support for SQL Server 2005 ended on April 12, 2011, with extended support concluding on April 12, 2016.

SQL Server 2008

Microsoft 2008, codenamed Katmai, was released on August 6, 2008, as a major update to the database management system, emphasizing advancements in data handling, security, and administrative automation. This version built upon the .NET integration introduced in SQL Server 2005 by introducing features that improved efficiency for handling , geospatial information, and resource allocation, while enhancing (T-SQL) capabilities for more sophisticated data operations. It was designed to integrate seamlessly with , leveraging the operating system's enhanced security and clustering features for better scalability in enterprise environments. A key innovation in SQL Server 2008 was the FILESTREAM feature, which enabled the storage and management of binary large objects (BLOBs) directly in the file system while allowing full transactional consistency through SQL Server. This approach addressed performance limitations of traditional BLOB storage in the database by combining file system speed with database properties, making it suitable for applications like document management and media storage. SQL Server 2008 also introduced native support for spatial data through the and data types, along with associated methods and spatial indexing. The type handled round-earth calculations for real-world locations, while supported planar (Euclidean) geometries, enabling applications in geographic information systems (GIS), mapping, and location-based services to perform queries like calculations and overlap detection directly in SQL. To manage resource contention in multi-workload environments, Resource Governor was added, allowing database administrators to classify sessions into resource pools and set limits on CPU, memory, and I/O usage. This feature provided predictable performance by preventing any single workload from monopolizing server resources, particularly useful in consolidated server setups. Enhancements to T-SQL included the MERGE statement, which combined INSERT, UPDATE, and DELETE operations into a single atomic statement based on a join condition between source and target tables. This simplified ETL processes and reduced the need for multiple conditional statements, improving code readability and performance in data synchronization scenarios. Additionally, (CDC) was introduced to asynchronously track insert, update, and delete operations on tables by reading the and storing changes in system tables for auditing or replication purposes. Policy-Based Management provided a declarative framework for enforcing configuration standards across SQL Server instances, using facets, conditions, and policies to evaluate and remediate settings like surface area configurations or backup compliance. This centralized approach reduced administrative overhead and ensured consistency in multi-server deployments. Mainstream support for SQL Server 2008 ended on July 8, 2014, with extended support concluding on July 9, 2019; however, Extended Security Updates were available until July 2022 for organizations needing additional time to migrate.

SQL Server 2008 R2

Microsoft SQL Server 2008 R2, codenamed Kilimanjaro, reached release to manufacturing on April 20, 2010, and became generally available shortly thereafter as an incremental release building on SQL Server 2008. This version emphasized advancements in business intelligence (BI), data management, and scalable data warehousing to support enterprise analytics needs. It introduced tools aimed at empowering business users with self-service capabilities while enhancing server-side processing for complex workloads. SQL Server 2008 R2 was the final version to provide native support for Itanium-based systems, aligning with the phasing out of IA64 architecture in subsequent Microsoft products. Extended support concluded on July 9, 2019, with Extended Security Updates available until July 12, 2022. A key addition was PowerPivot, a technology integrated directly into 2010 and Server 2010, allowing business analysts to import, manage, and analyze millions of rows of data without requiring IT intervention. PowerPivot leverages the in-memory columnar storage engine known as VertiPaq and the (DAX) query language to enable interactive PivotTables, data modeling, and compression for large datasets sourced from various feeds. This feature democratized BI by extending Analysis Services capabilities to desktop users, facilitating faster insights from disparate data sources. Master Data Services (MDS) was introduced as a comprehensive master data management solution, enabling organizations to create, maintain, and distribute a single, authoritative view of critical business entities such as products, customers, and accounts. MDS supports flexible hierarchies, business rules for data validation, versioning for audit trails, and role-based security, all accessible via a web-based interface and a Web services API for integration with custom applications. It helps ensure data consistency across systems, reducing errors in reporting and analytics. Complementing this, the Parallel Data Warehouse (PDW) appliance provided a turnkey, massively parallel processing (MPP) solution for terabyte- to petabyte-scale data warehousing, utilizing a shared-nothing architecture to distribute queries across multiple nodes for high performance and scalability. PDW integrates with standard SQL Server tools and supports direct data loading from external sources, targeting large enterprises needing appliance-based deployment without custom hardware configuration. StreamInsight debuted as a (CEP) platform for real-time on , such as inputs or financial transactions, using temporal SQL extensions for operations like joins, aggregations, and windowing over high-velocity event streams. It processes events at rates exceeding millions per second, enabling low-latency detection of patterns and anomalies in scenarios like fraud detection or monitoring. Reporting Services in SQL Server 2008 R2 saw enhancements including support for new data sources like SharePoint lists and the PDW appliance, along with improved visualizations such as sparklines, maps, and dynamic formatting options to make reports more interactive and embeddable in environments. These updates built on the spatial data types introduced in SQL Server 2008, allowing geographic visualizations in reports.

High Availability and Performance Focus

SQL Server 2012

Microsoft SQL Server 2012, codenamed during development, was generally available on April 1, 2012. This version emphasized enhancements in , mission-critical performance, and , building on prior releases to support enterprise-scale deployments. It introduced features aimed at reducing , improving query efficiency for analytical workloads, and simplifying database portability, positioning SQL Server as a robust platform for business-critical applications. A major advancement was Always On Availability Groups, which provided flexible and disaster recovery by allowing up to five replicas per group, including support for readable secondary replicas to offload reporting and backups. This feature replaced and extended database mirroring from earlier versions, enabling automatic failover and multi-site configurations without shared storage. Columnstore indexes were introduced to accelerate data warehousing queries, storing data in a columnar format that achieved up to 100 times better performance on analytics workloads through batch-mode processing and compression ratios up to 10 times higher than rowstore indexes. Contained databases further enhanced security and portability by isolating user authentication and metadata within the database itself, eliminating dependencies on instance-level logins and facilitating easier migrations across servers. Transact-SQL (T-SQL) saw key improvements for developer productivity, including the OFFSET and FETCH clauses for efficient in result sets, which allowed skipping a specified number of rows before fetching the next batch—essential for large-scale data retrieval without custom logic. The THROW statement was added for streamlined error handling, enabling developers to raise exceptions with a simple syntax that supports re-throwing from TRY...CATCH blocks and provides more precise error reporting than the deprecated RAISERROR. SQL Server 2012 was the final version to include native support for the provider via SQL Server Native Client 11.0, which handled connectivity for legacy applications; subsequent versions shifted to the separate Microsoft Driver for SQL Server. To address needs, Microsoft introduced the Business Intelligence Edition, which bundled all Standard Edition features with advanced BI tools like PowerPivot, Analysis Services tabular models, and Reporting Services data alerts, available at a per-server + CAL licensing model. Mainstream support for SQL Server 2012 ended on July 11, 2017, with extended support concluding on July 12, 2022; Extended Security Updates were available for three additional years, ending on July 8, 2025, to provide critical patches during migration.

SQL Server 2014

Microsoft SQL Server 2014, released on April 1, 2014, represented a significant advancement in database management by integrating in-memory capabilities and hybrid cloud functionalities, building on the features introduced in prior versions. Developed under the codename Hekaton for its in-memory components, this version aimed to enhance performance for (OLTP) workloads while enabling seamless integration with cloud services. It was the final release to support 32-bit (x86) architectures, marking the transition to 64-bit exclusivity in subsequent versions. A cornerstone feature was In-Memory OLTP, powered by the Hekaton , which introduced memory-optimized tables and natively compiled stored procedures to dramatically reduce latency and eliminate locking and latching overhead in high-throughput OLTP scenarios. This allowed tables to reside entirely in memory while maintaining full transactional consistency and through logging to disk, achieving up to 30 times the throughput of traditional disk-based OLTP in benchmarks. Memory-optimized tables could coexist with traditional rowstore and columnstore tables, enabling hybrid workloads without requiring a complete database redesign. SQL Server 2014 pioneered hybrid cloud integration with features like backup to Azure Blob Storage via , allowing direct writes of backups to without local intermediaries, and Managed Backup to , which automated backup scheduling based on data change rates. Stretch Database further extended this by enabling transparent migration of cold or historical data from on-premises tables to Azure SQL Database, where it remained queryable as if local, reducing storage costs and maintenance without application changes—though this feature was discontinued in July 2024. These capabilities facilitated a bridge between on-premises and environments, supporting disaster recovery and archival scenarios. Enhancements to Always On Availability Groups, originally introduced in SQL Server 2012, improved by supporting up to eight secondary replicas (doubled from four) and enhancing readable secondaries for multi-site deployments, allowing read workloads to be offloaded more effectively across distributed environments. Extended support for SQL Server 2014 ended on July 9, 2024, with Extended Security Updates available for up to three additional years until July 12, 2027, to provide critical security patches for legacy deployments.

SQL Server 2016

SQL Server 2016, codenamed , was released by on June 1, 2016, marking a significant evolution in database analytics, security, and hybrid integration. This version introduced native support for advanced data processing and monitoring features, building on prior in-memory OLTP capabilities from SQL Server 2014 to enhance overall performance and scalability. As the first SQL Server release exclusively supporting 64-bit (x64) processors, it discontinued compatibility with 32-bit (x86) systems, aligning with modern hardware trends and optimizing resource utilization. A key addition was built-in JSON support within (T-SQL), enabling developers to store, index, query, and modify data directly in the database without external processing. This facilitated easier integration with web and mobile applications by treating as a first-class , including functions for , validation, and extraction. Temporal tables, also known as system-versioned temporal tables, were introduced to automatically track historical data changes, maintaining a full with timestamps for each row modification, insertion, or deletion. These tables use a current table for live data and a linked history table for past versions, simplifying compliance and without custom triggers or application logic. SQL Server 2016 also debuted R Services (later renamed Services), allowing in-database execution of scripts for advanced and directly alongside relational data. This integration, powered by the Microsoft R Open distribution, enabled secure, scalable data science workflows by processing data in-place, reducing data movement and enhancing privacy for sensitive information. The Query Store feature provided always-on performance diagnostics by persistently capturing query text, execution plans, and runtime statistics, aiding in regression detection and plan forcing. It integrated with Always On Availability Groups, ensuring query insights across primary and readable secondary replicas for high-availability environments. Stretch Database received enhancements in this release, expanding its hybrid capabilities for archiving infrequently accessed ("cold") data to transparently and securely, while keeping active data on-premises. Features like row-level filtering and dynamic improved efficiency, allowing seamless querying across local and without application changes. SQL Server 2016 follows Microsoft's Fixed Lifecycle Policy, with mainstream support ending on July 13, 2021, and extended support concluding on July 14, 2026; Extended Security Updates are available for up to three additional years until July 17, 2029.

Cross-Platform and Cloud Era

SQL Server 2017

SQL Server 2017, version 14.0, marked a significant milestone in the evolution of Microsoft's by introducing native support for operating systems, expanding beyond its traditional Windows-centric deployment model. Released on October 2, 2017, this version enabled SQL Server to run directly on popular Linux distributions including 7.3 and later, Server v12 SP2 and later, and 16.04 and later, as well as in Docker containers for containerized environments. This cross-platform capability allowed organizations to leverage SQL Server's enterprise features in heterogeneous environments, supporting workloads such as , , and optimization on without requiring Windows hosts. A key enhancement in SQL Server 2017 was the expansion of Services to include Python integration, building on the language support introduced in the previous version. This feature enabled in-database execution of Python scripts using the stored procedure, allowing data scientists to perform advanced analytics, model training, and data processing directly within the while maintaining data security and reducing latency from data movement. Python support was available on Windows installations, with compatibility for popular libraries like and , though it was not enabled on in this release. SQL Server 2017 also introduced a preview of adaptive query processing, a family of intelligent query optimization techniques designed to improve for complex workloads by dynamically adjusting execution plans based on runtime statistics. These included batch mode adaptive joins, which switch between nested loop and strategies mid-execution; approximate distinct count using adaptive histograms for faster estimation; and interleaved execution for multi-statement table-valued functions to enhance parallelism. Additionally, the release added graph data processing extensions, integrating node and edge tables with and shortest_path T-SQL predicates to model and query complex relationships, such as social networks or recommendation engines, natively within the relational engine. Mainstream support for SQL Server 2017 ended on October 11, 2022, with extended support continuing until October 12, 2027.

SQL Server 2019

Microsoft SQL Server 2019 was released to general availability on November 4, 2019. This version marked a significant shift toward integrating relational databases with and capabilities, enabling organizations to analyze diverse data sources more efficiently. Building on Linux support introduced in SQL Server 2017, the 2019 release expanded cross-platform deployment options while emphasizing scalability and intelligence. A key innovation in SQL Server 2019 was the introduction of Big Data Clusters, which combine SQL Server with and Hadoop Distributed File System (HDFS) to form scalable, containerized clusters. These clusters allow users to process and query large-scale, polyglot data using familiar T-SQL syntax, supporting both relational and non-relational workloads in a unified environment. This feature facilitates on by integrating Spark for distributed processing and enabling across on-premises, , and edge scenarios. SQL Server 2019 also advanced AI integration through enhancements to Machine Learning Services, including the addition of Java Language Extensions. This extensibility framework permits the execution of Java code directly within the database, allowing developers to build and deploy machine learning models using Java libraries alongside and Python scripts. Such capabilities streamline AI workflows by keeping in-database, reducing latency and data movement. Intelligent Query Processing emerged as another cornerstone feature, comprising adaptive techniques like batch mode execution on rowstore tables and scalar user-defined function inlining to optimize query performance automatically. These AI-driven optimizations adjust based on workload patterns, improving efficiency for complex queries without manual tuning. Additionally, Unicode support was enhanced with native collations, enabling varchar columns to store Unicode characters while minimizing storage overhead for ASCII-dominant data and improving sorting for multilingual applications. To bolster reliability, SQL Server 2019 introduced Accelerated Database Recovery, which redesigns the transaction log recovery process to achieve near-instantaneous restarts after failures. By decoupling recovery from long-running transactions and using persistent versioning, this feature significantly reduces downtime in high-availability environments. Mainstream support for SQL Server 2019 ended on February 28, 2025, with extended support available until January 8, 2030; note that Big Data Clusters reached end-of-life on February 28, 2025.

SQL Server 2022

2022, codenamed , was generally available on November 16, 2022, marking a significant in Microsoft's management system with emphasis on security, seamless Azure integration, and capabilities for handling modern data workloads. This release builds on prior versions by introducing features that enhance , performance optimization, and hybrid cloud connectivity, enabling organizations to manage operational data alongside analytics without extensive infrastructure changes. A core security innovation is the feature, which provides tamper-proof tables through cryptographic verification and immutability guarantees, ensuring data cannot be altered without detection and supporting compliance in regulated environments. Complementing this, Query Store hints empower database administrators to influence query execution plans directly via the Query Store, eliminating the need for application code modifications while improving performance predictability. These tools address common challenges in maintaining secure and efficient database operations amid growing data volumes. For Azure integration, SQL Server 2022 introduces Azure Synapse Link, facilitating near real-time analytics on operational data by streaming changes to Azure Synapse Analytics without traditional ETL processes, thus reducing latency for hybrid scenarios. Enhanced distributed availability groups further bolster high availability by utilizing multiple TCP connections to optimize network bandwidth across geographically dispersed replicas. Additionally, integration with the Fabric preview enables mirrored databases for advanced analytics, allowing SQL Server instances to sync data continuously to Fabric's lakehouse architecture for unified data management. To support large-scale modern workloads, SQL Server 2022 adds approximate aggregate functions such as APPROX_PERCENTILE_CONT and APPROX_PERCENTILE_DISC, which compute interpolated percentiles efficiently on massive datasets with low memory overhead, ideal for scenarios involving approximate distinct value analysis without exact counts. Mainstream support for SQL Server 2022 ends on January 11, 2028, with extended support projected until January 11, 2033, during which cumulative updates including security fixes will continue to be provided.

SQL Server 2025

2025, version 17.0, was released to general availability on November 19, 2025, continuing the evolution toward AI-driven, cloud-integrated, and cross-platform database management. This release introduces over 40 new engine features, with a focus on built-in AI capabilities such as vector data types for workloads and enhanced support for developer flexibility across languages and environments. It maintains support for Windows and deployments, including Docker containers, while deepening integration with Azure services and Microsoft Fabric for hybrid and multi-cloud scenarios, including real-time synchronization and advanced without data movement. Security enhancements include improved and compliance tools, alongside performance optimizations for high-availability and large-scale processing. Reporting services are consolidated under Power BI Report Server for unified reporting. 2025 follows 's fixed lifecycle , with mainstream and extended support dates to be detailed in official documentation.

Architectural and Support Evolution

Processor Architectures

Microsoft SQL Server's initial releases, from version 1.0 in 1989 through version 6.0 in 1995, supported only and (x86) processor architectures, aligning with the dominant personal computing and early server hardware of the era. Starting with in 1996, broadened compatibility to include RISC-based processors, adding support for the , MIPS , and PowerPC alongside continued backing, enabling deployment on diverse non- hardware platforms running . Support for the MIPS was confined to this version and discontinued thereafter. compatibility persisted through SQL Server 7.0 in 1998, marking the final release for that architecture, while PowerPC support also ended around the same period. The , as a reduced instruction set computing (RISC) design, provided performance advantages in the early 1990s, particularly in integer and floating-point workloads, often outperforming equivalent systems due to its 64-bit capabilities and efficient pipeline. In 2003, the 64-bit edition of SQL Server 2000 introduced support for the () architecture, targeting enterprise-scale with explicit parallel instruction computing (EPIC). This compatibility extended through SQL Server 2008 R2, released in 2010, after which ceased support, citing the architecture's limited market adoption and the EPIC model's shortcomings, which depended on advanced compiler optimizations that failed to deliver promised scalability and efficiency in real-world database scenarios. Native x64 (AMD64) support became a core feature starting with SQL Server 2005, enhancing memory addressing and multi-processor scalability for large databases, while (x86) remained available for legacy environments. By SQL Server 2016, x86 support was fully deprecated, with installations restricted to x64 processors only to prioritize modern hardware capabilities and reduce compatibility overhead. ARM64 support emerged in preview form with Azure SQL Edge in 2019, a lightweight variant of the SQL Server engine optimized for IoT and edge devices, offering compatibility with ARM-based systems for low-power deployments. Full production support for ARM64 in Azure SQL Edge arrived in subsequent updates, including cumulative updates aligned with SQL Server 2022 timelines, though the edition was retired in September 2025 amid shifting focus to cloud-native alternatives.

Operating System and Deployment Support

Microsoft SQL Server's early development was tied to the operating system, with version 1.0 released in 1989 as a 16-bit specifically for , resulting from a joint effort between , Sybase, and . Support remained exclusive to through versions up to 4.2 in 1992. Beginning with version 4.21 in 1993, SQL Server extended compatibility to , marking the transition toward Windows as the primary platform. Following the end of the Microsoft-Sybase partnership around 1994, SQL Server 6.0 in 1995 shifted to an exclusive focus on Windows platforms, leveraging the Windows NT kernel for improved performance and stability. Throughout the 2000s, SQL Server versions aligned closely with Windows Server releases to optimize integration and resource utilization; for instance, SQL Server 2008 was designed for seamless deployment on Windows Server 2008, supporting features like failover clustering that relied on the underlying OS architecture. This alignment continued with subsequent releases, such as SQL Server 2012 on Windows Server 2012, ensuring compatibility with OS-specific advancements in scalability and security. A major expansion occurred with SQL Server 2017, introducing support for Linux distributions including Red Hat Enterprise Linux 7.3 and later, Ubuntu 16.04 LTS and later, and SUSE Linux Enterprise Server 12 SP2 and later, enabling cross-platform deployments without altering the core database engine. Docker container support was also added in 2017, allowing SQL Server to run in lightweight, portable environments on both Windows and Linux hosts using Docker Engine 1.8 or higher. SQL Server editions have evolved to address diverse deployment needs, starting with simple Standard and Enterprise tiers in early Windows-focused versions that differentiated primarily by scalability limits. With SQL Server 2005, introduced the free Express edition for developers and small-scale applications, alongside the Web edition tailored for internet service providers and hosting scenarios. These editions facilitated a shift from purely on-premises installations to hybrid models, with the introduction of Azure SQL Database in 2010 serving as a fully managed service that abstracts OS management entirely, acting as a precursor to broader cloud-native deployments. Key deployment milestones include the introduction of failover clustering in SQL Server 6.5 in 1996, which utilized clustering for high availability by allowing automatic failover across nodes. Container-based deployments via Docker followed in 2017, enhancing portability and orchestration. In 2019, SQL Server Big Data Clusters extended support to for scalable, distributed environments, integrating SQL Server with tools in or on-premises clusters. SQL Server 2025, released in November 2025, maintains support for x64 processors on 2025, distributions, and containerized environments, with enhanced integration for Azure Fabric.

References

  1. https://www.microsoft.com/en-us/sql-server/blog/2012/02/15/new-video-the-history-of-sql-server/
  2. https://learn.microsoft.com/en-us/sql/sql-server/what-is-sql-server?view=sql-server-ver17
  3. https://learn.microsoft.com/en-us/sql/connect/connect-history?view=sql-server-ver17
  4. https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/sql-server-end-of-support-overview?view=sql-server-ver17
  5. https://learn.microsoft.com/en-us/sql/reporting-services/reporting-services-consolidation-faq?view=sql-server-ver17
  6. https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates
  7. https://archive.computerhistory.org/resources/access/text/2016/12/102762677-05-01-acc.pdf
  8. https://www.networkworld.com/article/755586/microsoft-subnet-and-then-there-was-sybase.html
  9. https://www.omniloader.com/databases/sap-adaptive-server-enterprise
  10. https://archive.computerhistory.org/resources/access/text/2016/12/102762744-05-01-acc.pdf
  11. https://learn.microsoft.com/en-us/shows/history/history-of-microsoft-1989
  12. https://www.os2museum.com/wp/os2-history/os2-16-bit-server/
  13. https://www.sqlshack.com/history-sql-server-evolution-sql-server-features/
  14. https://www.latimes.com/archives/la-xpm-1991-07-11-fi-3022-story.html
  15. https://licenseware.io/history-of-microsoft-sql-server/
  16. https://www.theregister.com/2020/12/28/sql_server/
  17. https://www.nytimes.com/1999/05/24/business/oracle-takes-aim-at-two-small-software-rivals.html
  18. https://flylib.com/books/en/2.257.1.21/1/
  19. https://www.nytimes.com/1994/04/13/business/company-news-microsoft-and-sybase-change-arrangement-on-codes.html
  20. https://techmonitor.ai/technology/sybase_microsoft_explain_away_divorce
  21. https://sqlserverbuilds.blogspot.com/
  22. https://news.microsoft.com/source/1996/04/16/microsoft-ships-sql-server-6-5/
  23. https://www.brentozar.com/archive/2018/05/book-review-inside-sql-server-6-5/
  24. https://jimgray.azurewebsites.net/SQL_Scales.doc
  25. https://endoflife.date/mssqlserver
  26. https://stackoverflow.com/questions/3850687/comparing-and-contrasting-sybase-and-sql-server
  27. https://www.itprotoday.com/early-versions/what-s-new-in-sql-server-7-0-
  28. https://www.oreilly.com/library/view/microsoft-sql-server/9781118282175/c01_level1_1.xhtml
  29. https://news.microsoft.com/speeches/steve-ballmer-speech-transcript-launch-of-microsoft-sql-server-7-0-at-comdexfall-98/
  30. http://www.juelp.dk/wp-content/uploads/2016/10/inside-the-sql-server-query-optimizer.pdf
  31. https://learn.microsoft.com/en-us/sql/sql-server/what-s-new-in-sql-server-2000?view=sql-server-ver15
  32. https://esj.com/articles/1998/11/18/sql-server-launch-tests-microsoft.aspx
  33. https://news.microsoft.com/source/1999/12/13/microsoft-unveils-sql-server-2000-windows-2000-integration/
  34. https://news.microsoft.com/source/1999/01/12/microsoft-announces-backoffice-server-4-5/
  35. https://www.vldb.org/conf/1999/P25.pdf
  36. https://sigmodrecord.org/publications/sigmodRecord/9806/pdfs/276305.276378.pdf
  37. https://news.microsoft.com/source/1999/06/14/microsoft-access-2000-clientserver-features-now-available-to-enable-easier-integration-with-sql-server/
  38. https://rcpmag.com/articles/2002/05/08/gartner-2001-not-2000-was-sql-servers-year.aspx
  39. https://news.microsoft.com/source/2000/08/07/microsoft-sql-server-2000-enters-production-ships-to-early-adopters/
  40. https://learn.microsoft.com/en-us/archive/msdn-magazine/2000/august/sql-server-2000-new-features-provide-unmatched-ease-of-use-and-scalability-to-admins-and-users
  41. https://sqlserverbuilds.blogspot.com/2000/01/sql-server-2000-versions.html
  42. https://learn.microsoft.com/en-us/archive/msdn-magazine/2000/march/sql-server-2000-new-xml-features-streamline-web-centric-app-development
  43. https://learn.microsoft.com/en-us/archive/msdn-magazine/2003/october/olap-asp-net-sql-server-2000-analysis-services-and-office-xp
  44. https://www.informit.com/articles/article.aspx?p=31359&seqNum=224
  45. https://www.red-gate.com/simple-talk/databases/sql-server/t-sql-programming-sql-server/edition-sql-server-best-development-work/
  46. https://learn.microsoft.com/en-us/archive/msdn-magazine/2002/january/sql-server-2000-and-xml-developing-xml-enabled-data-solutions-for-the-web
  47. https://learn.microsoft.com/en-us/sql/relational-databases/clr-integration/common-language-runtime-integration-overview?view=sql-server-ver17
  48. https://learn.microsoft.com/en-us/sql/relational-databases/xml/xml-data-type-and-columns-sql-server?view=sql-server-ver17
  49. https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/sql-server-service-broker?view=sql-server-ver17
  50. https://learn.microsoft.com/en-us/lifecycle/products/microsoft-sql-server-2005
  51. https://learn.microsoft.com/en-us/archive/msdn-magazine/2009/september/sql-server-2005-service-broker-microsoft%25E2%2580%2599s-new-messaging-technology
  52. https://news.microsoft.com/source/2005/02/24/microsoft-announces-expanded-sql-server-2005-product-line-to-meet-customers-growing-demands/
  53. https://learn.microsoft.com/en-us/sql/connect/ado-net/sql/sql-server-express-user-instances?view=sql-server-ver17
  54. https://www.brentozar.com/archive/2008/08/sql-server-2008-release-date-today/
  55. https://sqlserverbuilds.blogspot.com/2008/01/sql-server-2008-versions.html
  56. https://www.mssqltips.com/sqlservertip/2254/sql-server-2008-list-of-new-features/
  57. https://www.red-gate.com/simple-talk/databases/sql-server/learn/sql-server-2008-the-new-data-types/
  58. https://learn.microsoft.com/en-us/sql/relational-databases/resource-governor/resource-governor?view=sql-server-ver17
  59. https://www.databasejournal.com/ms-sql/10-new-sql-server-2008-features/
  60. https://learn.microsoft.com/en-us/sql/t-sql/statements/merge-transact-sql?view=sql-server-ver17
  61. https://learn.microsoft.com/en-us/sql/relational-databases/track-changes/about-change-data-capture-sql-server?view=sql-server-ver17
  62. https://www.mssqltips.com/sqlservertip/1474/using-change-data-capture-cdc-in-sql-server-2008/
  63. https://learn.microsoft.com/en-us/sql/relational-databases/policy-based-management/administer-servers-by-using-policy-based-management?view=sql-server-ver17
  64. https://www.mssqltips.com/sqlservertip/1492/using-policy-based-management-in-sql-server/
  65. https://learn.microsoft.com/en-us/lifecycle/products/microsoft-sql-server-2008
  66. https://learn.microsoft.com/en-us/previous-versions/troubleshoot/sql/install/end-support-sql-server-2008
  67. https://news.microsoft.com/source/2010/04/21/microsoft-kicks-off-worldwide-launch-of-sql-server-2008-r2/
  68. https://www.microsoft.com/en-us/windows-server/blog/2010/04/02/windows-server-2008-r2-to-phase-out-itanium
  69. https://learn.microsoft.com/en-us/lifecycle/products/microsoft-sql-server-2008-r2
  70. https://download.microsoft.com/download/c/d/1/cd1648c1-46bc-4c79-b16f-7af650c186b4/693883ebook.pdf
  71. https://blogs.microsoft.com/blog/2012/03/07/microsoft-sql-server-2012-reaches-rtm/
  72. https://www.brentozar.com/archive/2012/03/sql-server-release-date-april/
  73. https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server?view=sql-server-ver17
  74. https://learn.microsoft.com/en-us/sql/relational-databases/indexes/columnstore-indexes-query-performance?view=sql-server-ver17
  75. https://learn.microsoft.com/en-us/sql/relational-databases/databases/contained-databases?view=sql-server-ver17
  76. https://www.mssqltips.com/sqlservertip/2362/overview-of-offset-and-fetch-feature-of-sql-server-2012/
  77. https://learn.microsoft.com/en-us/sql/t-sql/language-elements/throw-transact-sql?view=sql-server-ver17
  78. https://learn.microsoft.com/en-us/sql/connect/oledb/applications/support-policies-for-oledb-driver-for-sql-server?view=sql-server-ver17
  79. https://download.microsoft.com/download/7/3/c/73cad4e0-d0b5-4be5-ab49-d5b886a5ae00/sql_server_2012_licensing_reference_guide.pdf
  80. https://learn.microsoft.com/en-us/lifecycle/products/microsoft-sql-server-2012
  81. https://blogs.microsoft.com/blog/2014/03/18/sql-server-2014-released-to-manufacturers-will-be-generally-available-april-1/
  82. https://learn.microsoft.com/en-us/answers/questions/5605658/change-sql-database-32bit-to-64bit
  83. https://www.microsoft.com/en-us/sql-server/blog/2013/07/22/architectural-overview-of-sql-server-2014s-in-memory-oltp-technology/
  84. https://learn.microsoft.com/en-us/sql/relational-databases/in-memory-oltp/sql-server-in-memory-oltp-internals-for-sql-server-2016?view=sql-server-ver17
  85. https://download.microsoft.com/download/B/C/C/BCC5F3C4-BB4D-458C-BAA7-23C1FD52CCCC/SQL_Server_2014_In-Memory_OLTP_TDM_White_Paper.pdf
  86. https://learn.microsoft.com/en-us/sql/relational-databases/backup-restore/sql-server-backup-to-url?view=sql-server-ver17
  87. https://www.microsoft.com/en-us/sql-server/blog/2014/07/24/get-started-backing-up-to-the-cloud-with-sql-server-backup-to-microsoft-azure-tool/
  88. https://www.microsoft.com/en-us/sql-server/blog/2024/07/03/announcing-the-retirement-of-sql-server-stretch-database/
  89. https://www.microsoft.com/en-us/sql-server/blog/2013/06/27/alwayson-in-sql-server-2014-ctp1/
  90. https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2014
  91. https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/extended-security-updates-frequently-asked-questions?view=sql-server-ver17
  92. https://www.microsoft.com/en-us/sql-server/blog/2016/06/01/sql-server-2016-is-generally-available-today/
  93. https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2016
  94. https://learn.microsoft.com/en-us/sql/sql-server/what-s-new-in-sql-server-2016?view=sql-server-ver17
  95. https://learn.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server?view=sql-server-ver17
  96. https://learn.microsoft.com/en-us/sql/relational-databases/tables/temporal-tables?view=sql-server-ver17
  97. https://learn.microsoft.com/en-us/sql/machine-learning/r/sql-server-r-services?view=sql-server-2016
  98. https://learn.microsoft.com/en-us/sql/relational-databases/performance/monitoring-performance-by-using-the-query-store?view=sql-server-ver17
  99. https://www.sqlskills.com/blogs/erin/query-store-and-availability-groups/
  100. https://redmondmag.com/articles/2017/09/25/microsoft-launches-sql-server-2017.aspx
  101. https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup?view=sql-server-ver17
  102. https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-release-notes-2017?view=sql-server-ver17
  103. https://learn.microsoft.com/en-us/sql/machine-learning/sql-server-machine-learning-services?view=sql-server-ver17
  104. https://learn.microsoft.com/en-us/shows/microsoftr/sql-server-2017-gets-python-support-in-new-machine-learning-services
  105. https://learn.microsoft.com/en-us/sql/machine-learning/what-s-new-in-sql-server-machine-learning-services?view=sql-server-ver17
  106. https://www.microsoft.com/en-us/sql-server/blog/2017/09/28/enhancing-query-performance-with-adaptive-query-processing-in-sql-server-2017/
  107. https://www.microsoft.com/en-us/sql-server/blog/2017/04/20/graph-data-processing-with-sql-server-2017/
  108. https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2017
  109. https://www.microsoft.com/en-us/sql-server/blog/2019/11/04/sql-server-2019-is-now-generally-available/
  110. https://www.microsoft.com/en-us/sql-server/blog/2019/11/04/gain-intelligence-over-data-with-sql-server-2019-now-generally-available/
  111. https://learn.microsoft.com/en-us/sql/sql-server/what-s-new-in-sql-server-2019?view=sql-server-ver17
  112. https://www.microsoft.com/en-us/sql-server/blog/2018/09/25/introducing-microsoft-sql-server-2019-big-data-clusters/
  113. https://www.sqlshack.com/overview-of-sql-server-2019-general-availability-and-installation/
  114. https://learn.microsoft.com/en-us/sql/language-extensions/install/windows-java?view=sql-server-ver17
  115. https://www.sqlshack.com/java-language-extensions-in-sql-server-2019/
  116. https://nielsberglund.com/post/2020-12-29-bring-your-own-r--python-runtimes-to-sql-server-extensibility-framework/
  117. https://learn.microsoft.com/en-us/sql/relational-databases/performance/intelligent-query-processing?view=sql-server-ver17
  118. https://www.sqlservercentral.com/blogs/native-utf-8-support-in-sql-server-2019-savior-or-false-prophet
  119. https://learn.microsoft.com/en-us/sql/relational-databases/accelerated-database-recovery-concepts?view=sql-server-ver17
  120. https://www.mssqltips.com/sqlservertip/5971/accelerated-database-recovery-in-sql-server-2019/
  121. https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2019
  122. https://www.microsoft.com/en-us/sql-server/blog/2022/11/16/sql-server-2022-is-now-generally-available/
  123. https://sqlserverbuilds.blogspot.com/2021/07/sql-server-2022-versions.html
  124. https://learn.microsoft.com/en-us/sql/sql-server/what-s-new-in-sql-server-2022?view=sql-server-ver17
  125. https://learn.microsoft.com/en-us/sql/relational-databases/security/ledger/ledger-overview?view=sql-server-ver17
  126. https://learn.microsoft.com/en-us/sql/relational-databases/performance/query-store-hints?view=sql-server-ver17
  127. https://learn.microsoft.com/en-us/azure/synapse-analytics/synapse-link/sql-synapse-link-overview
  128. https://learn.microsoft.com/en-us/fabric/mirroring/sql-server
  129. https://learn.microsoft.com/en-us/sql/t-sql/functions/approx-percentile-cont-transact-sql?view=sql-server-ver17
  130. https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2022
  131. https://techcommunity.microsoft.com/blog/sqlserver/sql-server-2025-is-now-generally-available/4470570
  132. https://learn.microsoft.com/en-us/sql/sql-server/what-s-new-in-sql-server-2025?view=sql-server-ver17
  133. https://www.databasejournal.com/ms-sql/sql-server-6-5-and-sql-server-7-0-compared/
  134. https://www.route-fifty.com/digital-government/1996/06/new-sql-server-65-still-serves-only-windows-nt-environments/280233/
  135. https://www.itprotoday.com/it-infrastructure/the-death-of-alpha-on-nt
  136. https://news.microsoft.com/source/2003/04/24/new-64-bit-sql-server-2000-enhances-performance-and-scalabilityof-the-microsoft-platform/
  137. https://arstechnica.com/information-technology/2010/04/microsoft-its-the-end-of-the-line-for-itanium-support/
  138. https://redmondmag.com/articles/2005/05/07/sql-server-2000-service-pack-4-released.aspx
  139. https://sqlha.com/32-bit-server-based-sql-server-is-finally-dead/
  140. https://learn.microsoft.com/en-us/azure/azure-sql-edge/resources-partners-security
  141. https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/sql_scales.doc
  142. https://community.sap.com/t5/additional-blog-posts-by-sap/a-deeper-look-at-sybase-history-of-ase/ba-p/12923660
  143. https://learn.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2019?view=sql-server-ver17
  144. https://learn.microsoft.com/en-us/sql/linux/quickstart-install-connect-docker?view=sql-server-ver17
  145. https://learn.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2022?view=sql-server-ver17
  146. https://www.microsoft.com/en-us/sql-server/blog/2025/01/15/the-year-ahead-for-sql-server-ground-to-cloud-to-fabric/
  147. https://www.sqlservercentral.com/articles/why-every-sql-server-installation-should-be-a-cluster-1
  148. https://www.neowin.net/news/microsoft-announces-general-availability-of-sql-2025-fabric-databases-and-documentdb/
Add your contribution
Related Hubs
User Avatar
No comments yet.