Skip to content

sql-server-end-of-support-overview.md

Latest commit

 

History

History
289 lines (208 loc) · 26.2 KB

sql-server-end-of-support-overview.md

File metadata and controls

289 lines (208 loc) · 26.2 KB
title End of Support Options
description Learn about the different options available for SQL Server products that reach end of support, including SQL Server 2014.
author rwestMSFT
ms.author randolphwest
ms.date 12/20/2025
ms.service sql
ms.subservice install
ms.topic concept-article
monikerRange >=sql-server-2016

SQL Server end of support options

[!INCLUDE SQL Server]

This article explains your options for addressing [!INCLUDE ssnoversion-md] products that reach end of support.

Understand the SQL Server lifecycle

Each version of [!INCLUDE ssNoVersion] comes with a minimum of 10 years of support, which includes five years of mainstream support and five years of extended support:

  • Mainstream support includes functional, performance, scalability, and security updates.
  • Extended support includes only security updates.

End of support (also sometimes known as end of life) means that a product reached the end of its lifecycle. Microsoft no longer provides servicing and support for the product. For more information about the Microsoft Lifecycle, see Microsoft Lifecycle Policy.

Options

When your [!INCLUDE ssNoVersion] instance reaches the end of support, choose from the following options:

For more information, guidance, and tools to plan and automate your upgrade or migration, see:

The following table provides migration options for a [!INCLUDE ssnoversion-md] instance that is out of extended support and running on-premises.

Migration option Description
Modernize to Azure
Move to PaaS with Azure SQL Managed Instance Lift and shift to SQL Managed Instance for fully managed services that always run evergreen features. In other words, the end of support doesn't apply.
Move to IaaS with SQL Server on Azure VM Upgrade to latest SQL Server on Azure VMs, or move [!INCLUDE sssql14-md] "as-is", and get three years of Extended Security Updates for free.
Move to Azure VMware Solution Move "as-is" with SQL Server out of extended support, and get three years of Extended Security Updates for free.
Modernize on-premises
Upgrade on-premises Upgrade to the latest versions of SQL Server and Windows Server.
Stay on-premises
Purchase extended security updates Keep server and application as-is for up to three years.

This article describes the benefits and considerations for each approach, with more resources to help guide your decision-making process.

Upgrade SQL Server

When your [!INCLUDE ssNoVersion] instance reaches the end of support, consider upgrading to a newer supported version of [!INCLUDE ssNoVersion]. This option provides environmental consistency, lets you use the latest features, and aligns you with the new version's support lifecycle.

Benefits

  • Latest technology: New [!INCLUDE ssNoVersion] versions bring innovations in performance, scalability, high availability, and security.

  • Control: You have the most control over features and scalability, because you manage both hardware and software.

  • Familiar environment: If you're upgrading from an older version of [!INCLUDE ssNoVersion], this environment feels the most familiar.

  • Wide applicability: Suitable for all kinds of database applications, including OLTP systems and data warehousing.

  • Low risk for database applications: When the database compatibility matches the legacy system, existing database applications stay protected from functional and performance changes. An application only needs full recertification when it requires features available under a newer database compatibility setting. For more information, see Compatibility certification.

Considerations

  • Cost: This approach requires the largest up-front investment and the most ongoing management. You must buy, maintain, and manage your own hardware and software.

  • Downtime: Depending on your upgrade strategy, downtime might occur. There's also an inherent risk of running into problems during an in-place upgrade process.

  • Complexity: If you're on an unsupported version of Windows Server, you also need to upgrade the OS. Newer versions of [!INCLUDE ssNoVersion] might not support those Windows versions. There's added risk during the OS upgrade process, so doing a side-by-side migration might be the more prudent, yet more costly, approach. In-place OS upgrades aren't supported on failover cluster instances for Windows Server 2008 or [!INCLUDE winserver2008r2-md].

    [!NOTE]
    Cluster OS rolling upgrades are available starting with Windows Server 2016.

Resources

What's new in:

Hardware requirements:

Supported version and edition upgrades:

Tools:

Azure SQL Managed Instance

If you want to offload maintenance and reduce costs but find the feature set of [!INCLUDE ssazure-sqldb] too limiting, consider moving to Azure SQL Managed Instance. A SQL managed instance closely resembles an on-premises [!INCLUDE ssNoVersion] instance, without the need to worry about hardware failure or patching. SQL Managed Instance is a collection of system and user databases with a shared set of resources that is lift-and-shift ready and can be used for most migrations to the cloud. This option is best for new applications or existing on-premises applications that want to use the latest stable [!INCLUDE ssDEnoversion] features and that are migrated to the cloud with minimal changes.

Benefits

  • Cost: You save costs by offloading software and hardware maintenance.
  • Lift and shift: You can lift and shift your entire [!INCLUDE ssNoVersion] on-premises instance to a SQL managed instance, including all databases with minimal to no database change.
  • Features: It closely matches the features of an on-premises instance of [!INCLUDE ssNoVersion], such as cross-database queries, transactional replication publishing and distribution, SQL job scheduling, and CLR support.
  • Scalability: Within a SQL managed instance, all databases share resources, and you can scale up and down at any time without downtime.
  • Automation: Patching and backups happen automatically, saving you valuable maintenance time.
  • Availability: The cost of the service includes both storage and high availability, with 99.99% availability guaranteed.
  • Intelligent Insights: Gain insight about the performance of your databases with built-in intelligence analytics.
  • Versionless: Azure SQL Managed Instance is versionless, meaning you're always on the latest version, and never have to worry about upgrading or downtime. Plus, you're always on the latest and greatest, with the latest stable features being released to the cloud first.
  • Low risk for database applications: When the database compatibility is at the same level as the on-premises databases, existing database applications are protected from functional and performance changes that can have detrimental effects. An application only needs to be fully recertified when it requires features available in a newer database compatibility setting. For more information, see Compatibility certification.

Considerations

  • Cost: SQL managed instance can be more costly than Azure SQL Database.
  • Transact-SQL differences: Some [!INCLUDE tsql] (T-SQL) differences exist between SQL managed instance and on-premises [!INCLUDE ssNoVersion].
  • Deployment: Deploying a SQL managed instance can take more time than deploying a single database.
  • Feature limitation: Although a SQL managed instance shares most features with [!INCLUDE ssNoVersion], some features are unsupported.
  • Size limitation: The combined storage size for all databases within a SQL managed instance is limited to 32 TB, as opposed to 524 PB for on-premises [!INCLUDE ssNoVersion].
  • Networking: The networking requirements for a SQL managed instance add an extra layer of complexity to your infrastructure and require either an Azure ExpressRoute or VPN Gateway.
  • Maintenance time: You have no guarantee for the exact maintenance time, though it's nearly transparent.

Resources

Tools:

Extend support

If you're not ready to upgrade, and you're not ready to move to the cloud, you have the ability to purchase an Extended Security Updates subscription to receive Critical security updates for up to three years past the end of the support date.

Benefits

  • Application support: This option is the best choice if your application requires recertification on a newer version of [!INCLUDE ssNoVersion]. This option is common for applications that don't use Compatibility certification.
  • Consistent infrastructure: You don't need to change your infrastructure in any way.
  • Technical support: If you have Software Assurance, or another support plan, you can continue receiving technical support from [!INCLUDE msCoName] on your end-of-support [!INCLUDE ssNoVersion] product. This option is the only way to get support for [!INCLUDE sssql14-md].
  • Time: This option is available for three years, giving you extra time to certify your applications.

Considerations

  • Limited availability: Only customers with Software Assurance or subscription licenses can use this option.
  • Cost: This option can prove costly, as Extended Security Updates are approximately 75% of the on-premises license cost annually.
  • Limited time frame: You can use this option for only three years. You need to upgrade or migrate at the end of the three-year period to ensure your security and compliance.
  • No bug fixes: If you encounter a non-security bug with the product, [!INCLUDE msCoName] won't release a fix for it.
  • Limited support: Extended Security Updates don't include new features, functional improvements, or customer-requested fixes. Security fixes are limited to fixes rated as Critical by the Microsoft Security Response Center (MSRC).

Resources

SQL Server on Azure VMs

Another option is to migrate your workload to an Azure Virtual Machine running SQL Server. You can migrate your system as-is and keep your end-of-support [!INCLUDE ssNoVersion], or you can upgrade to a newer version of [!INCLUDE ssNoVersion]. This option is best for migrations and applications requiring OS-level access. [!INCLUDE ssNoVersion] virtual machines are lift-and-shift ready for existing applications that require fast migration to the cloud with minimal or no changes.

Benefits

  • Free Extended Security Updates: If you choose to keep your [!INCLUDE ssNoVersion] as-is, using [!INCLUDE sssql14-md], you can get free Extended Security Updates for three years past the end of support date, even without having Software Assurance.
  • Cost-saving: You save the cost of hardware and server software, only paying for hourly usage.
  • Lift-and-shift: You can lift and shift your [!INCLUDE ssNoVersion] and application infrastructure into the cloud with minimal or no changes.
  • Hosted environment: You get the benefits of a hosted environment, such as offloading hardware and software maintenance.
  • Automation: If you're on [!INCLUDE winserver2008r2-md] and later versions, you get the benefit of automated patching and automated backups.
  • OS Control: You have control over the operating system environment, but with the familiar feature set of [!INCLUDE ssNoVersion].
  • Rapid deployment: You can quickly deploy from a library of virtual machine images.
  • License mobility: You can bring your license, allowing you to decrease operating cost.
  • High availability: You benefit from the built-in virtual machine availability by the Azure infrastructure with up to 99.99% availability, and take advantage of [!INCLUDE ssNoVersion] high availability options such as failover cluster instances and Always On availability groups.
  • Low risk for database applications: When the database compatibility is at the same level as the legacy databases, existing database applications are protected from functional and performance changes that can have detrimental effects. An application only needs to be fully recertified when it requires features available under a newer database compatibility setting. For more information, see Compatibility certification.

Considerations

  • Manageability: You still have to manage both [!INCLUDE ssNoVersion] and operating system software.
  • Networking: You have to configure the virtual machine to integrate with your networking and Active Directory infrastructure, which is an added layer of complexity.
  • Shared storage FCI: Azure virtual machines only support failover cluster instances using Storage Spaces Direct or Premium File Shares, and don't support a failover cluster instance using shared storage. As such, Azure virtual machines only support failover cluster instances when using Windows Server 2012 and later versions.
  • Scalability downtime: You have downtime while changing the CPU and storage resources.
  • Size limitation: Although the [!INCLUDE ssNoVersion] instance can support as many databases as needed, the cumulative total of all databases for a single instance of [!INCLUDE ssNoVersion] is 256 TB, as opposed to 524 PB for an on-premises [!INCLUDE ssNoVersion].

Resources

Azure VMware Solution

Azure VMware Solution allows you to run your VMware environment in Azure by using familiar tooling and a quick migration path.

Running SQL Server in VMs in this environment provides you with the free ESU benefits extended to running in Azure. For information on how to configure ESUs in Azure VMware Solution, review: ESUs for SQL Server and Windows Server in Azure VMware Solution VMs.

Azure SQL Database

If you want to offload maintenance, reduce costs, and eliminate the need to upgrade in the future, move your workload to Azure SQL Database. This option is best for modern cloud applications that want to use the latest stable [!INCLUDE ssDEnoversion] features and have time constraints in development and marketing.

Benefits

  • Cost: A single database can be cost-effective, since you offload hardware, software, and maintenance costs, and you pay for usage by the second or the hour.
  • Flexibility: A single database is well suited for cloud-designed applications when developer productivity and fast time-to-market solutions are critical, or that require external access.
  • Common features: The most commonly used [!INCLUDE ssDEnoversion] features are available, but not as many as for Azure SQL Managed Instance.
  • Rapid deployment: You can quickly deploy a single database.
  • Scalability: You can quickly and easily scale up and down as needed for your business, providing more cost-saving benefits.
  • Availability: The cost of the service includes both storage and high availability, with 99.995% availability guaranteed.
  • Automation: Patching and backups happen automatically, saving you valuable maintenance time.
  • Intelligent Insights: Gain insight about the performance of your database with built-in intelligence analytics.
  • Versionless: [!INCLUDE ssazure-sqldb] is versionless, meaning you're always on the latest version, and never have to worry about upgrading or downtime. Plus, you're always on the latest and greatest, with our latest stable features being released to the cloud first.
  • Low risk for database applications: When the database compatibility is at the same level as the on-premises database, existing applications are protected from functional and performance changes that can have detrimental effects. An application only needs to be fully recertified when it requires features available under a newer database compatibility setting. For more information, see Compatibility certification.

Considerations

  • Limited migration options: You can only migrate a single database at a time, rather than an entire instance.
  • Feature limitation: Although the most commonly used Azure SQL Database features are available, the feature set for a database isn't as complete as for Azure SQL Managed Instance, or [!INCLUDE ssNoVersion].
  • Transact-SQL differences: There are some [!INCLUDE tsql] (T-SQL) differences between a database and an on-premises [!INCLUDE ssNoVersion].
  • Size limitations: A single database has a maximum database size of 128 TB, compared to 524 PB for [!INCLUDE ssNoVersion].
  • Maintenance time: You have no guarantee for the exact maintenance time, though it's nearly transparent.

Resources

Tools:

Lifecycle dates

The following table provides an approximation of lifecycle dates for [!INCLUDE ssNoVersion] products. For greater details and accuracy, see the Microsoft Lifecycle Policy page.

Version Release year Mainstream Support end year Extended Support end year
SQL Server 2025 2025 2031 2036
SQL Server 2022 2022 2028 2033
SQL Server 2019 2019 2025 2030
SQL Server 2017 2017 2022 2027
SQL Server 2016 2016 2021 2026
SQL Server 2014 2014 2019 2024

Important

If any discrepancy exists between this table and the [!INCLUDE msCoName] Lifecycle page, the [!INCLUDE msCoName] Lifecycle page supersedes this table. This table is intended as an approximate reference.

Related content