SQL Server 2016 End of Life: Plan Your Upgrade Before the First Year of Extended Security Updates Ends in July 2027

SQL Server 2016 End of Life: Plan Your Upgrade Before the First Year of Extended Security Updates Ends in July 2027

SQL Server 2016 extended support ended on 14 July 2026. If your business is using Extended Security Updates (ESUs) to keep an eligible environment protected, the first ESU year ends on 13 July 2027.

From October 2026, that leaves around nine months for your organisation to complete an upgrade before Year 2. If you are responsible for the platform, the decision is now about choosing a supported destination and finding a team to deliver the work around your business.

At Pro DBA, we bring 30 years of specialist database experience to your project. Database migrations and upgrades are a core part of our work.

Our UK SQL Server team can scope and carry out your upgrade, working with your staff and application suppliers to agree testing and change windows. You can also retain 24/7 SQL Server support after the move.

SQL Server 2016 ESU dates for Years 1 to 3

Microsoft lists the following end dates for SQL Server 2016 ESU coverage.

• Year 1: 13 July 2027
• Year 2: 18 July 2028
• Year 3: 17 July 2029

These are programme dates. Joining later does not give your organisation a new three-year period. Your actual cover also depends on eligibility and an active ESU subscription.

For businesses aiming to leave ESUs after the first year, July 2027 is the target completion date. Organisations intending to retain coverage through Years 2 and 3 have a longer window, but still need a route to a supported platform.

What the first ESU year means for your upgrade project

ESUs provide security updates rated Critical by Microsoft when those updates are available. They do not restore normal product support, add new features or include customer-requested non-security fixes.

That matters when SQL Server supports a business application your team cannot easily replace. An ESU arrangement gives you time to resolve dependencies and prepare a migration, while the underlying need to move remains.

If your goal is to finish before Year 2, appointing a provider early leaves room for application vendor approvals, infrastructure changes and a test migration. It also gives your team time to review the scope and approve a realistic change window.

For example, an application vendor may require certification on a particular SQL Server version. A database upgrade proposal should identify that dependency before delivery dates are agreed.

Need a team to carry out your SQL Server 2016 upgrade? Talk to our SQL Server team about your current environment, ESU position and target completion date.

Planning to use ESUs for two or three years

If your organisation intends to retain ESU coverage through July 2028 or July 2029, your project can follow a longer timetable. That may be useful when an application replacement, infrastructure programme or supplier dependency needs more time.

The useful question is what that extra time will achieve. A longer ESU plan should have a migration owner, an agreed destination and milestones for removing the dependencies that keep SQL Server 2016 in production.

Compare the future cost of retaining ESUs with the full upgrade proposal, including licences, infrastructure, testing and support. The purpose of that comparison is to choose a workable transition date, with the budget and supplier work needed to reach it.

Pro DBA can help scope a phased database migration where the environment and application dependencies allow it. That gives your team a defined project to commission even when different systems need to move at different times.

Choosing the right SQL Server upgrade destination

A supported SQL Server version

Microsoft supports upgrade paths from SQL Server 2016 Service Pack 3 or later to SQL Server 2022 and SQL Server 2025 on Windows, subject to the supported edition and platform requirements. An intermediate upgrade to SQL Server 2017 or 2019 is not always required.

Your application vendor’s support position, feature use, operating system and licensing should shape the choice. We can review the database requirements with your team and help establish the target environment before the migration is scheduled.

A move to Azure

Microsoft also identifies Azure SQL Managed Instance, Azure SQL Database and SQL Server on Azure virtual machines as migration options. They have different feature support and management responsibilities, so the choice needs to fit your workload.

Moving an unchanged SQL Server 2016 instance to an Azure VM does not itself upgrade the Database Engine. Retaining it still requires the appropriate ESU arrangement.

If a cloud move is part of your wider plans, Pro DBA offers SQL Server cloud migration services covering assessment, design, testing and the live migration.

What your SQL Server upgrade proposal should cover

A SQL Server upgrade needs to account for the applications and services that depend on the instance. Moving user databases alone can leave gaps where logins, SQL Server Agent jobs or other server-level objects are required. Those dependencies should be covered in the migration scope.

Before commissioning the work, your proposal should answer four practical questions:

• Which applications and integrations will be tested, and who will approve the results?
• What planned service interruption is acceptable, and how will the estimate be validated?
• What is the recovery plan if the change cannot be completed as agreed?
• Who will monitor and support the environment after it goes live?

The upgrade method affects the answers. An in-place upgrade changes the existing installation and requires downtime. A migration to a new environment allows preparation alongside the current system, but still needs a planned cutover. Microsoft notes that downtime depends on factors including database size and storage performance.

For technical teams, the scope should also distinguish the engine upgrade from changes to database compatibility level. Microsoft’s guidance uses Query Store and a performance baseline to help assess the effect of those changes. A proposed project should include workload testing and a response plan for performance regressions.

Recovery needs its own design. Backups from a newer SQL Server version cannot be restored to an older version, so a rollback plan cannot rely on restoring the upgraded database straight back to SQL Server 2016. Backup restore testing should also be part of the agreed preparation.

Why choose Pro DBA for your SQL Server upgrade

When you commission a SQL Server upgrade, you need a provider that understands both migration delivery and the demands of a production database. Our experience carrying out upgrades and migrations helps us identify the dependencies, testing and recovery arrangements that need to be agreed before the live change.

Our SQL Server consultants can take on the database upgrade or migration work, working with your internal team and application suppliers. The scope can cover the existing database review, migration planning, test migrations, support for application regression testing and the live move.

The project should give your CTO and technical leads a defined set of deliverables:

• A review of the current database environment, feature use and migration feasibility.
• A proposed target environment and a technical migration plan.
• Test migration results and support for application validation.
• An agreed live migration window and documented delivery plan.
• A clear handover and arrangements for support after the move.

Our involvement can continue after go-live. We can support an existing DBA team or provide ongoing SQL Server management through our own UK 24/7 service desk. Services include monitoring, patch management, backup management, restore testing and performance investigation, giving your team access to database specialists after the upgrade as well as during it.

Your application owners will still need to confirm business requirements and approve application testing. Agreeing those responsibilities at the start helps your team understand what Pro DBA will deliver and what input the project needs from you.

What determines the cost and timescale

An upgrade proposal needs to reflect the environment and the amount of work around it. A small standalone instance and a group of production databases with availability requirements, integrations and supplier approvals need different scopes.

The main cost and scheduling factors include:

• The number of instances and databases, their sizes and feature use.
• The target SQL Server edition, licensing position and infrastructure requirements.
• Application compatibility, vendor involvement and the amount of testing.
• Availability requirements, migration method and permitted change windows.
• The support required during the move and after go-live.

For a July 2027 target, the first conversation should establish the database scope and any external dependencies that could determine the delivery date. Once those are understood, the work can be quoted and scheduled against your ESU plan.

Talk to Pro DBA about your SQL Server 2016 upgrade

Whether you aim to finish before July 2027 or intend to use Years 2 and 3, our team can plan and carry out the database move, backed by 30 years of experience and ongoing SQL Server support.

Tell us how many instances you run, the applications they support and your target date. Our team can discuss your migration options and how Pro DBA can carry out the upgrade for you.

Talk to our SQL Server team