History & Editions of SQL Server
Trace SQL Server's origins from its 1989 partnership with Sybase through the major releases that shaped the product, and see how its editions look today.
Introduction
SQL Server is now decades old, and understanding a bit of its history helps explain why it looks the way it does today — why it shares DNA with Sybase, why it is so tightly bound to Windows conventions, and why recent versions suddenly added Linux support. This lesson is a fast, practical tour: enough history to make sense of the product, without turning into a trivia lecture.
Origins
Microsoft SQL Server's story begins in 1989, when Microsoft, Sybase, and Ashton-Tate jointly released SQL Server 1.0 for OS/2. At that point, Microsoft did not have its own database engine — the product was essentially a port of Sybase SQL Server to the OS/2 platform, marketed under the Microsoft name. Ashton-Tate dropped out of the partnership after the first release.
The Sybase Partnership
Microsoft and Sybase continued to co-develop SQL Server through the early 1990s. Microsoft ported the engine to Windows NT, which was a major turning point — it gave Microsoft a database that ran natively on its own emerging server operating system, rather than depending on OS/2 or UNIX. The partnership formally ended in 1994, and each company went on to develop its own SQL Server product independently. Microsoft's fork became the SQL Server we know today; Sybase's became Sybase ASE (Adaptive Server Enterprise).
This shared ancestry is why older T-SQL syntax occasionally resembles Sybase conventions rather than pure ANSI SQL — for example, the historical use of the older-style join syntax and system tables that trace back to that common codebase.
Major Milestones
| Year | Release | Significance |
|---|---|---|
| 1989 | SQL Server 1.0 | First release, joint effort with Sybase, for OS/2 |
| 1993 | SQL Server 4.2 | First version ported to Windows NT |
| 1998 | SQL Server 7.0 | Complete rewrite of the storage engine, first fully Microsoft-built core |
| 2005 | SQL Server 2005 | Introduced SSMS as the modern management tool, replacing Enterprise Manager |
| 2012 | SQL Server 2012 | Added AlwaysOn Availability Groups for high availability |
| 2016 | SQL Server 2016 | Native JSON support, Always Encrypted, Query Store |
| 2017 | SQL Server 2017 | First version to run natively on Linux and in Docker containers |
| 2019+ | SQL Server 2019 / 2022 | Big data clusters, Azure Arc integration, continued cloud convergence |
The 2017 release is worth calling out specifically: it marked the end of SQL Server being a Windows-only product. Today, the same T-SQL you write runs unchanged whether the engine is hosted on Windows Server, a Linux VM, a Docker container, or as the managed Azure SQL Database service.
Today's Editions
The modern SQL Server product line still follows the same shape introduced decades ago — a tiered set of editions for different needs — but now includes fully cloud-hosted options.
- SQL Server Express — free, capped at 10 GB per database, ideal for learning and small applications.
- SQL Server Developer — free, full Enterprise feature set, licensed for development and testing only (not production).
- SQL Server Standard — paid, core database engine features for small-to-medium production workloads.
- SQL Server Enterprise — paid, the full feature set including advanced high-availability and performance features for mission-critical systems.
- Azure SQL Database — a fully managed, pay-as-you-go cloud database service; no server to patch or maintain.
-- You can check which edition and version you're running with:SELECT @@VERSION;Click Run to see what this code prints.
Common Mistakes
- Assuming SQL Server has always been Windows-only — Linux/Docker support has existed since 2017.
- Deploying Developer Edition to a production server because it 'has all the features for free' — its license explicitly forbids production use.
- Confusing SQL Server version numbers (like 16.0) with marketing year names (like SQL Server 2022) when reading documentation.
- Ignoring edition limits, such as Express's 10 GB per-database cap, when planning a real project.
Best Practices
- Always confirm which edition and build you're running with SELECT @@VERSION; before troubleshooting version-specific behavior.
- Use Developer Edition locally so you can experiment with Enterprise-only features risk-free.
- When reading older forum answers or blog posts, check the SQL Server version mentioned — syntax and best practices have shifted over 30+ years.
- Plan for Azure SQL Database early if you know the project will eventually move to the cloud — some on-prem-only features aren't available there.
Frequently Asked Questions
Microsoft, Sybase, and Ashton-Tate co-developed the original SQL Server in 1989. Microsoft and Sybase split their codebases apart in 1994, but the shared origin explains some of the similarities you'll still see between T-SQL and Sybase's SQL dialect.
SQL Server 2017, released in 2017, was the first version with official native Linux support and Docker images.
Yes, completely free, and it includes the full Enterprise feature set. The only restriction is licensing: it may only be used for development, testing, and demonstration, not for production workloads.
Azure SQL Database is a managed cloud service built on the SQL Server engine. Microsoft handles patching, backups, and infrastructure; you interact with it purely through T-SQL and connection strings, without managing a server.
Key Takeaways
- SQL Server began in 1989 as a joint project between Microsoft, Sybase, and Ashton-Tate.
- Microsoft and Sybase split their codebases in 1994, giving rise to two separate database products.
- SQL Server 2017 was the first release to officially support Linux and Docker.
- Today's edition lineup ranges from free (Express, Developer) to paid on-prem (Standard, Enterprise) to fully managed cloud (Azure SQL Database).
Summary
You've traced SQL Server from its 1989 Sybase-era roots to its modern, cross-platform, cloud-ready form. Next, you'll look at why SQL Server specifically is worth learning — the career and technical reasons it remains one of the most in-demand database skills.