SQL Server 2016 support ended on 14 July 2026, so there are no more free security fixes. You have four choices, and the right one depends on whether your server is Express, Standard or Enterprise, what Windows version it runs, and whether a vendor application, jobs or SSIS packages depend on it.
Check what you have first
Run this query in SQL Server Management Studio. It reads server details and counts related items. It does not change anything.
-- 1. The server: version, update level, edition.
-- 13.x = SQL Server 2016, 14.x = 2017, 15.x = 2019, 16.x = 2022, 17.x = 2025.
SELECT SERVERPROPERTY('MachineName') AS server_name,
SERVERPROPERTY('ProductVersion') AS product_version,
SERVERPROPERTY('ProductLevel') AS product_level,
SERVERPROPERTY('ProductUpdateLevel') AS update_level,
SERVERPROPERTY('Edition') AS edition;
-- 2. The databases: size, compatibility level (130 = SQL Server 2016) and owner.
SELECT d.name, d.compatibility_level, d.state_desc, d.recovery_model_desc,
SUSER_SNAME(d.owner_sid) AS owner,
CAST(SUM(mf.size) * 8 / 1024.0 AS decimal(12,1)) AS size_mb
FROM sys.databases d
JOIN sys.master_files mf ON mf.database_id = d.database_id
WHERE d.database_id > 4
GROUP BY d.name, d.compatibility_level, d.state_desc, d.recovery_model_desc, d.owner_sid
ORDER BY d.name;
-- 3. What else lives on the server and must move with it.
SELECT 'SQL Server Agent jobs' AS item, COUNT(*) AS how_many FROM msdb.dbo.sysjobs
UNION ALL SELECT 'Logins (not built in)', COUNT(*) FROM sys.server_principals
WHERE type IN ('S','U','G') AND name NOT LIKE '##%' AND name NOT LIKE 'NT %' AND name <> 'sa'
UNION ALL SELECT 'Linked servers', COUNT(*) FROM sys.servers WHERE is_linked = 1
UNION ALL SELECT 'Database Mail profiles', COUNT(*) FROM msdb.dbo.sysmail_profile
UNION ALL SELECT 'SSIS packages stored in msdb', COUNT(*) FROM msdb.dbo.sysssispackages p
LEFT JOIN msdb.dbo.sysssispackagefolders f ON f.folderid = p.folderid
WHERE ISNULL(f.foldername, '') <> 'Data Collector'
UNION ALL SELECT 'SSIS catalog (SSISDB) present', COUNT(*) FROM sys.databases WHERE name = 'SSISDB'
UNION ALL SELECT 'Credentials', COUNT(*) FROM sys.credentials
UNION ALL SELECT 'Agent proxies', COUNT(*) FROM msdb.dbo.sysproxies;
A product version beginning with 13. means SQL Server 2016. ProductLevel tells you whether it has SP3, which is required before an upgrade or Extended Security Updates. ProductUpdateLevel shows whether a cumulative update is installed. The edition determines which options you can buy.
The database rows show size, status, recovery model, compatibility level and owner. Compatibility level 130 means the database still uses SQL Server 2016 behavior. The remaining counts find items outside the databases that also need attention.
Tested on: SQL Server 2025 Standard Developer, version 17.0.1000.7 (RTM), 14 November 2026.
| Server | Version | Product level | Update level | Edition |
|---|---|---|---|---|
| TEST-SQL | 17.0.1000.7 | RTM | (no CU) | Standard Developer Edition (64-bit) |
| Database | Compatibility | State | Recovery | Owner | Size |
|---|---|---|---|---|---|
| LabLegacy2016 | 130 | ONLINE | FULL | TEST-SQL\owner | 16.0 MB |
| What lives on it | Count |
|---|---|
| SQL Server Agent jobs | 1 |
| Logins (not built in) | 1 |
| Linked servers | 0 |
| Database Mail profiles | 0 |
| SSIS packages stored in msdb | 0 |
| SSIS catalog present | 0 |
| Credentials | 0 |
| Agent proxies | 0 |
We ran the query on SQL Server 2025, so its version begins with 17. A SQL Server 2016 result begins with 13. The database owner in our test is a person’s Windows account. That can become a problem when the person leaves, as explained in The person who ran your data left.
Your four choices
Stay where you are and accept the risk
The server keeps running after support ends. Microsoft no longer provides normal security updates or technical support, and SQL Server 2016 customers cannot open support tickets even with a support plan. Microsoft warns that running without fixes can create security and compliance problems in its end of support overview.
This may be a short holding position for a system already scheduled for retirement. It is not a supported long-term plan.
Pay for Extended Security Updates
Extended Security Updates provide Critical security fixes for up to three years, through July 2029. They do not add features or general product fixes. Only Standard and Enterprise editions qualify. Express, Web and Developer editions do not, according to Microsoft’s SQL Server ESU FAQ.
The server must have SP3 and the latest update. You can buy a monthly subscription after connecting it to Azure Arc, or buy annual coverage through volume licensing with active Software Assurance. Connecting the server to Azure Arc is free, but it requires an outbound connection to Azure. The monthly subscription can be canceled at any time. Microsoft explains the routes and prerequisites on its ESU page.
Microsoft’s Azure Arc pricing page listed SQL Server 2016 ESUs at $277.40 per 2-core pack per month for Standard and $1,080.40 for Enterprise. Those were Central US list prices in US dollars on 14 November 2026, and Microsoft labels them as estimates.
All physical cores are billed, with a four-core minimum. Our arithmetic puts a four-core Standard server at 2 × $277.40, or about $554.80 a month at list price. Standard billing is capped at 24 cores.
Joining late does not avoid earlier charges. A customer who enrolls in January 2027 receives a one-time bill for July through December 2026 in the first month, as Microsoft shows in its back-billing example.
Upgrade to SQL Server 2022 or 2025
SQL Server 2016 SP3 can upgrade directly to SQL Server 2022 or SQL Server 2025. You can upgrade the existing installation or build a new server and move to it.
A side-by-side move keeps the old server available while you test the new one. Greg Low gives a useful explanation of this fallback advantage in his SQL Server 2016 upgrade guide.
SQL Server 2022 is supported until January 2033. SQL Server 2025 is supported until January 2036.
Move to Azure
Azure SQL Database and Azure SQL Managed Instance do not reach end of support, so they do not need ESUs. Managed Instance usually needs fewer application changes. SQL Server on an Azure virtual machine is the closer fit when you need operating system access or specific server components. Microsoft compares these choices in its Azure SQL service guide.
Moving SQL Server 2016 to an Azure virtual machine does not make its ESUs free. Microsoft ended that benefit for SQL Server 2016, as stated on the Azure VM ESU page.
Which choice fits your server
You have Express edition
Express cannot receive ESUs. SQL Server 2016 SP3 Express can upgrade directly to SQL Server 2025 Express, Standard or Enterprise.
SQL Server 2025 Express allows up to 50 GB per database, compared with 10 GB in SQL Server 2022 Express. It still does not include SQL Server Agent. Check the SQL Server 2025 edition limits against the database sizes and job count from your query.
A vendor application uses the database
Ask the vendor which SQL Server versions and editions it supports. Also ask whether it has tested the application at compatibility level 130 on the newer server.
ESUs can buy time while the vendor certifies SQL Server 2022 or 2025. If the vendor supports the newer server with compatibility level 130, you can move first and change database behavior later.
Windows Server 2016 is underneath it
Windows Server 2016 support ends on 12 January 2027, only six months after SQL Server 2016 support ended. Moving just the database engine may leave you with another support decision almost immediately.
SQL Server 2025 requires Windows Server 2019 or later. SQL Server 2022 runs on Windows Server 2016, but that does not extend support for the operating system. A new server with a supported Windows version usually gives you a cleaner path.
Jobs, SSIS packages or linked servers share the box
A database backup does not contain every server-level item. Logins, SQL Server Agent jobs, linked servers, Database Mail, credentials, proxies and SSIS packages need their own move plan. Microsoft lists many of these items in its server metadata guidance.
Target choice matters. Azure SQL Managed Instance supports SQL Server Agent and Database Mail, with limits on linked servers. Azure SQL Database uses different approaches for instance-level features. Microsoft’s feature comparison also explains how SSIS packages can run in a managed SSIS environment in Azure Data Factory.
For SQL Server 2025, test existing linked servers because some configurations can fail with the newer OLE DB driver. Microsoft documents that linked server change. Also check packages that run in 32-bit mode, which is deprecated in SSIS 2025.
One database must stay while the rest moves
Move the databases that are ready and keep the exception on SQL Server 2016 temporarily. Check for cross-database queries, shared jobs and linked servers before splitting them.
If the remaining database stays on an eligible SQL Server 2016 edition, ESU billing still covers all physical cores on that server. A smaller dedicated target may change the cost comparison.
Before you upgrade
-
Take full backups and test a restore on the new SQL Server version. A backup is only useful when you know it restores and the application can connect.
-
Record the edition, version, update level, database owners, sizes and compatibility levels. Script or document the logins, jobs, linked servers, Database Mail profiles, SSIS packages, credentials and proxies.
-
Keep the old server intact until the new one is proven. A backup made on a newer SQL Server version cannot be restored to an older version, so copying new production data back is not a rollback plan.
-
Leave compatibility level 130 in place for the first move. SQL Server preserves that level after the upgrade, and SQL Server 2025 supports levels 100 through 170. Raise it later, on purpose, after testing the application and reports. Microsoft explains this behavior in its compatibility level documentation.
The tools Microsoft offers now
Data Migration Assistant retired on 16 July 2025, and Azure Data Studio retired on 28 February 2026. Microsoft now offers the free Azure Arc migration assessment, migration components in SQL Server Management Studio, and Azure Migrate for discovery at scale. Azure Database Migration Service moves data but does not perform the assessment.
When to hand it over
Hand the move over when the vendor, Windows version and server-level items create several linked decisions, or when nobody can own the test and rollback plan. With our Move it to the cloud service, we assess the server, move it, and check that the numbers match on both sides.
Frequently asked questions
What happens after SQL Server 2016 end of support?
The server keeps running, but Microsoft no longer provides free security fixes or normal technical support. You must accept that risk, buy ESUs, upgrade the server or move the databases.
How much do SQL Server 2016 Extended Security Updates cost?
Microsoft’s list price was $277.40 per 2-core pack each month for Standard and $1,080.40 for Enterprise on 14 November 2026. A four-core Standard box is about $554.80 a month by our arithmetic. Microsoft bills at least four cores and back-bills late enrollment to the start of the current ESU year.
Can I upgrade SQL Server 2016 directly to SQL Server 2025?
Yes, if SQL Server 2016 has SP3 and the edition follows a supported upgrade path. SQL Server 2025 also needs Windows Server 2019 or later. A side-by-side move is often safer because it preserves the old server during testing.
Can SQL Server 2016 Express get Extended Security Updates?
No. Microsoft limits SQL Server 2016 ESUs to Standard and Enterprise editions. Express can move directly to SQL Server 2025 Express, Standard or Enterprise after SQL Server 2016 SP3 is installed.
How we checked this: every date, price and rule on this page was checked on Microsoft Learn, the Microsoft lifecycle pages and the Azure pricing page on 14 November 2026. We ran the inventory query on our own test server (SQL Server 2025 Standard Developer) the same day.
