SQL Server lifecycle support

Windows Managed Server is dependent on Microsoft’s lifecycle support. This document will review Microsoft’s policy and then cover Windows Managed Server’s policy.

Microsoft lifecycle support

SQL Server releases fall into one of two servicing models based on version and the relative lifecycle position of that specific SQL Server version. Microsoft’s modern lifecycle policy has a mainstream support lifecycle of 5 years, 5 additional years of extended support, then eligibility to purchase 3 additional years of Extended Security Updates (ESU). Where a product is in this overall support lifecycle impacts what types of releases are available and the type of support Microsoft provides.

After the mainstream support period has ended, Microsoft will provide support and security updates, but no quality or enhancement updates or other features can be expected. When a server falls beyond Extended Support without Extended Security Updates or beyond ESU it can no longer be kept up to date for security vulnerabilities–at this time it is in violation of UW policies.

More from Microsoft: detailed information on SQL Server end of support options. Supplements to that specifically related to SQL server are the fixed lifecycle policy, What are Extended Security Updates for SQL Server?, SQL2012 lifecycle, SQL 2014, SQL2016, SQL 2017, SQL2019, SQL2022.

Windows Managed Server lifecycle support for SQL Server

UW Administrative Policy Statements (APS) expect system owners & operators to keep all IT systems updated with vendor supplied security patches. So to be in alignment with UW expectations, software which is no longer eligible to receive security updates is considered in violation of UW expectations.

Windows Managed Server provisions servers with the latest SQL Server version to maximize the time the server will be supported. In-place SQL version upgrades are not supported; SQL version upgrades require requesting a new server. UW-IT must purchase an ESU support plan for any servers not retired at the end of extended support in order to continue operating them. UW-IT may also need to purchase additional support packages to maintain other security applications, for example for antivirus support. Any additional costs incurred due to running a server in extended support are passed along to customers.

Microsoft SQL Server licensing is available to employees and students on computers owned by the UW, via a Microsoft campus agreement through May 30, 2026. Beyond that date, the UW expects the costs to increase significantly beyond the ability for this product to be centrally funded. Customers using Microsoft SQL Server will likely have to pay for their use at that point. Customers are strongly encouraged to explore migrations to Azure SQL managed instance before that time. Windows Managed Server may have to recharge customers for SQL Server licensing in the future, but that doesn’t affect our lifecycle support.

The Windows Managed Server service uses five categories[1] to define our support for a given version of SQL Server:

• Emerging: Newest release which we are preparing to support; we aren’t ready to support this version yet and services/support may be subject to consulting rates.
• Baseline: Fully supported and preferred for new server builds.
• Containment: Fully supported for existing servers. Customers should begin making plans to retire and replace with a server in Baseline.
• Retirement: Scheduled for end-of-life. Customers are actively executing a plan to retire and replace with a server in Baseline. Windows Managed Server will purchase ESUs for any server which requires it, but the cost will be passed along to the customer.
• Unsupported: Not supported by Windows Managed Server. Servers in this category are shut down.

[1] The UW Enterprise Architecture (EA) program promotes using specific terms to communicate technology lifecycle states, and we use their terminology in describing our support practices and lifecycle process.