SQL Server 2016 has reached end of life. Compare upgrade, Azure, AWS and ESU options to secure your databases and build a practical modernisation roadmap with WinCap.
Microsoft SQL Server 2016 reached the end of Extended Support on 14 July 2026. Organisations still running this version must now decide whether to upgrade, migrate to a managed database service, move to cloud infrastructure or purchase Extended Security Updates while preparing a longer-term modernisation plan.
This is more than a routine technology refresh. Databases often support critical ERP systems, financial platforms, customer applications, reporting environments and operational workflows. Continuing to depend on an unsupported database platform can increase security exposure and make future application, infrastructure and compliance decisions more difficult.
As both a Microsoft and AWS partner, WinCap helps organisations evaluate the available options without assuming that one destination is right for every workload.
What Does SQL Server 2016 End of Life Mean?
Microsoft uses “end of support” or “end of life” to describe the point at which a product reaches the end of its support lifecycle. Once that happens, Microsoft no longer provides normal servicing and support for the product.
For SQL Server 2016, this does not mean that existing databases immediately stop working. It does mean that businesses can no longer rely on the normal support lifecycle for continued protection and assistance.
Organisations that need additional time can purchase Extended Security Updates, but Microsoft describes ESUs as a last-resort, temporary bridge rather than a long-term operating model.
Extended Security Updates: A Temporary Bridge
Eligible SQL Server 2016 environments can receive Extended Security Updates for up to three years after the end of Extended Support.
Microsoft lists the following ESU dates:
- ESU Year 1: until 13 July 2027
- ESU Year 2: until 18 July 2028
- ESU Year 3: until 17 July 2029
These updates are limited to security vulnerabilities classified as Critical by the Microsoft Security Response Center. They do not include new features, functional improvements, customer-requested fixes or standard technical support. Microsoft also states that ESUs are released only if and when qualifying vulnerabilities are identified, so there is no regular ESU release schedule. [learn.microsoft.com], [learn.microsoft.com]
What if SQL Server 2016 is running on AWS?
Running SQL Server 2016 on AWS or another non-Azure environment does not automatically provide free ESUs.
Microsoft allows organisations to purchase ESUs through the Azure portal regardless of their hosting infrastructure. Servers hosted outside Azure must generally be connected to Azure Arc. Once connected, eligible SQL Server instances can subscribe to ESUs, which may then be installed automatically when automatic updating is enabled.
Microsoft also supports manual registration for eligible SQL Server instances that cannot be connected directly to Azure Arc, subject to the documented prerequisites and licensing conditions.
Importantly, Microsoft states that, beginning with SQL Server 2016, moving a workload to SQL Server on Azure Virtual Machines no longer provides free access to SQL Server 2016 ESUs.
ESUs can therefore reduce immediate security exposure, but they should accompany a defined upgrade or migration roadmap.
Four Practical Modernisation Paths
The right path depends on the application, database features, existing licences, business continuity requirements, internal skills and wider cloud strategy.
Option 1: Upgrade to a Supported Version of SQL Server
For businesses that need or prefer to retain self-managed infrastructure, upgrading to a supported version of SQL Server may be the most direct route.
Microsoft identifies upgrading to a current SQL Server release as one of its principal end-of-support options. The target environment may remain on-premises or run on supported cloud infrastructure, depending on the organisation’s requirements.
This route may be appropriate when:
- The application depends on SQL Server functionality that is unavailable in a particular managed service.
- The organisation requires extensive operating-system or database-instance control.
- Data residency, connectivity or latency requirements favour an existing environment.
- A cloud migration forms part of a later transformation phase.
An in-place upgrade should not be assumed to be risk-free. Application dependencies, database compatibility levels, integrations, SQL Server Agent jobs, reporting services and third-party software should be assessed and tested before production cutover.
Option 2: Modernise on Microsoft Azure
Microsoft provides several potential destinations for SQL Server workloads, including:
- Azure SQL Managed Instance
- Azure SQL Database
- SQL Server on Azure Virtual Machines
Azure SQL Managed Instance
Azure SQL Managed Instance may suit organisations seeking a managed database service while retaining broad compatibility with SQL Server workloads.
It can provide a migration route for applications that need SQL Server instance-level capabilities but where the organisation wants to reduce responsibility for the underlying database infrastructure.
Azure SQL Database
Azure SQL Database provides a platform-as-a-service option for applications that can operate at the database level and do not require all the instance-level capabilities of a traditional SQL Server deployment.
This route can be particularly relevant when database migration is part of a broader application-modernisation programme rather than a direct infrastructure replacement.
SQL Server on Azure Virtual Machines
SQL Server on Azure VMs provides greater operating-system and instance-level control than a managed database platform. It can support a lift-and-shift approach or an upgrade to a supported SQL Server version during migration.
The trade-off is that an infrastructure-as-a-service deployment retains more administrative responsibility than a fully managed database service.
Option 3: Move to Amazon RDS for SQL Server
For businesses aligned with AWS, Amazon RDS for SQL Server offers a managed SQL Server environment.
AWS provides both Licence Included and eligible Bring Your Own Media licensing routes. With BYOM, qualifying customers can use existing SQL Server Enterprise or Standard Edition licences that have the applicable licence-mobility rights.
Amazon RDS can take responsibility for elements of the database platform such as automated patching, backups, monitoring and high-availability infrastructure. Customers remain responsible for areas including their applications, data, identity design, access controls, configuration choices and migration validation.
Can existing applications move unchanged?
Moving between SQL Server environments may reduce the degree of code change compared with changing the database engine entirely. However, “no application changes” should never be assumed.
Amazon RDS for SQL Server has documented feature limitations and differences from a self-managed SQL Server instance. A migration assessment should examine:
- SQL Server features and editions in use
- Linked servers and external integrations
- SQL Server Agent jobs
- Authentication and Active Directory dependencies
- SSIS, SSRS and SSAS requirements
- Administrative and operating-system access
- Backup, recovery and high-availability requirements
- Application connection and latency requirements
These checks determine whether Amazon RDS, RDS Custom or self-managed SQL Server on Amazon EC2 represents the closest technical fit.
Bring Your Own Media on Amazon RDS
AWS introduced BYOM for organisations that want to reuse qualifying SQL Server licences on managed Amazon RDS infrastructure.
AWS documentation states that BYOM customers provide their SQL Server installation media and use the corresponding licensing model when creating the database instance. Available versions must match the installation media and AWS-supported configuration.
AWS also documents an in-place conversion path from Licence Included Amazon RDS for SQL Server instances to BYOM, without requiring a database migration. SQL Server Enterprise or Standard Edition with licence mobility is required for the documented conversion scenario.
A licensing review remains essential. Software Assurance, licence mobility, edition, core entitlements and contractual conditions should be validated before claimed savings are included in the business case.
Option 4: Run a Hybrid or Phased Modernisation Programme
Not every database needs to move to the same destination or on the same schedule.
An organisation might:
- Upgrade a latency-sensitive application on-premises.
- Move a compatible workload to Azure SQL Managed Instance.
- Migrate an AWS-aligned application to Amazon RDS for SQL Server.
- Run a specialist workload on SQL Server in Azure or Amazon EC2.
- Use ESUs temporarily for a database that cannot yet be upgraded.
A phased migration can help businesses prioritise databases according to security exposure, business criticality, technical complexity and infrastructure renewal dates.
The key is to avoid allowing ESUs or temporary hosting arrangements to become an undefined permanent state.
Choosing a SQL Server Migration Method on AWS
The migration mechanism is just as important as the destination.
Depending on downtime, database size and compatibility requirements, AWS migration patterns can include:
- Native SQL Server backup and restore
- AWS Database Migration Service
- A combination of full backup and ongoing replication
- Log-based or change-data-capture migration patterns
AWS documentation describes full-backup cutovers in which a database is backed up, transferred to Amazon S3 and restored to Amazon RDS. AWS notes that downtime for this method is affected by database size and the time needed to back up, transfer and restore the database.
Where a full-backup maintenance window is not acceptable, AWS DMS can be considered for replicating ongoing changes using change data capture.
Migration duration cannot be reliably determined from database size alone. It also depends on:
- Network throughput
- Transaction and change rates
- Permitted downtime
- Application dependencies
- Feature compatibility
- Security and connectivity approvals
- Testing and reconciliation requirements
- The number of migration rehearsals
- Cutover and rollback planning
For that reason, fixed claims such as “a 2–5 TB estate will migrate in 8–14 weeks” should be presented only as WinCap delivery estimates based on a completed assessment, not as Microsoft- or AWS-published guidance.
Building a Credible Cost Comparison
A meaningful comparison between on-premises SQL Server, Azure and AWS must extend beyond virtual-machine or database-instance prices.
The assessment should include:
- SQL Server licence entitlements
- Windows Server licensing, where applicable
- Compute and storage
- Backup and recovery
- High availability and disaster recovery
- Monitoring and security
- Network transfer and connectivity
- Database-administration effort
- Infrastructure operations
- Migration and testing costs
- Commitment-based cloud discounts
- Existing Microsoft licensing benefits
- Applicable cloud-migration incentives
Organisations should avoid publishing universal claims such as “Amazon RDS costs 30–50% more than EC2”. The result varies significantly according to licence model, instance configuration, storage, availability design, utilisation, operational labour and commercial commitments.
A stronger business case compares defined architectures over an agreed term and records every licensing, infrastructure and staffing assumption.
H2: Can AWS Funding Support the Migration?
Eligible migrations may receive support through AWS migration programmes, but funding should not be described as guaranteed.
The final amount and form of support depend on the customer, qualifying opportunity, approved migration scope, eligible services and applicable AWS programme terms. Any funding assumption should therefore be confirmed with AWS or an authorised AWS migration partner before it is included in a board-level ROI calculation.
Claims such as “AWS funds 20–40% of every SQL Server migration” should not be used without opportunity-specific written validation.
How WinCap Can Help
SQL Server 2016 End of Life is not simply an Azure decision or an AWS decision. It is a workload, risk, licensing and business-continuity decision.
As a Microsoft and AWS partner, WinCap can help organisations:
- Discover SQL Server 2016 instances across on-premises and cloud environments
- Map databases to applications, integrations and business owners
- Assess SQL Server feature and version compatibility
- Review ESU requirements and Azure Arc connectivity options
- Compare supported SQL Server upgrade paths
- Evaluate Azure SQL Managed Instance, Azure SQL Database and Azure VMs
- Assess Amazon RDS for SQL Server, Amazon EC2 and relevant AWS migration services
- Review Licence Included, BYOM and licence-mobility considerations
- Develop migration waves, testing plans and rollback strategies
- Build an evidence-based total-cost-of-ownership comparison
- Establish a modernisation roadmap aligned with business priorities
The objective is not to force every database into one platform. It is to place each workload on the environment that provides the appropriate balance of compatibility, security, control, resilience and cost.
The Best Time to Act Is Now
SQL Server 2016 has already reached the end of its standard support lifecycle.
Extended Security Updates can provide a temporary security bridge until 17 July 2029, but they do not add functionality, extend the product lifecycle or replace a long-term modernisation strategy.
Organisations should now identify affected databases, confirm whether ESUs are required, assess application dependencies and compare supported Microsoft and AWS migration destinations.
A structured assessment provides the evidence needed to select the right path, protect critical systems and prevent a temporary exception from becoming a long-term business risk.
Ready to Modernise Your SQL Server Environment?
WinCap can help you assess your SQL Server 2016 estate and compare upgrade, Microsoft Azure, AWS and hybrid options.
Speak with WinCap to create a practical SQL Server modernisation roadmap based on your applications, licences, security requirements and business priorities.
Frequently Asked Questions on About SQL Server 2016 End of Life and Migration
1. Is SQL Server 2016 still supported?
No. SQL Server 2016 reached the end of Extended Support on 14 July 2026. Eligible organisations can purchase Extended Security Updates as a temporary measure.
2. How long are SQL Server 2016 ESUs available?
Microsoft lists three ESU years for SQL Server 2016, with the final year ending on 17 July 2029.
3. Are SQL Server 2016 ESUs free on Azure?
No. Microsoft states that, starting with SQL Server 2016, migration to SQL Server on Azure Virtual Machines does not provide free access to SQL Server 2016 ESUs.
4. Can SQL Server 2016 on AWS receive ESUs?
Eligible SQL Server instances hosted outside Azure can subscribe through Azure Arc. Microsoft also documents a registration route for qualifying instances that cannot connect directly to Azure Arc.
5. Can SQL Server workloads move to Amazon RDS?
Amazon RDS supports SQL Server, including Licence Included and eligible BYOM deployment models. Compatibility should be assessed because managed database environments do not provide the same level of access or feature availability as every self-managed SQL Server configuration.
6. Should we choose Azure or AWS for SQL Server modernisation?
The answer depends on application compatibility, existing cloud architecture, Microsoft licensing, operational requirements, internal skills and total cost of ownership. A workload-by-workload assessment is more reliable than selecting one destination for the entire estate.