SQL Server 2017 End of Support: What to Know Before October 2027

Organizations running Microsoft SQL Server 2017 have more than a year before support officially ends, but now is the time to begin planning. SQL Server upgrades often involve application testing, infrastructure reviews, licensing decisions, and migration planning that can take months to complete.

Microsoft has announced that SQL Server 2017 will reach end of support on October 12, 2027. After that date, organizations will no longer receive security updates, bug fixes, or technical support unless they purchase Extended Security Updates (ESUs) or migrate to eligible Azure services.

For small and mid-sized businesses, SQL Server 2017 end of support is an opportunity to evaluate whether an upgrade to SQL Server 2025 or a move to Azure aligns better with long-term business and technology goals.

When Does SQL Server 2017 Reach End of Support?

According to Microsoft's official lifecycle policy, SQL Server 2017 reaches end of support on October 12, 2027.

After this date:

• No new security updates will be released.
• No non-security updates will be provided.
• Microsoft technical support will no longer be available.
• Compliance and audit requirements may become more difficult to satisfy.

Organizations can review Microsoft's lifecycle documentation on the SQL Server 2017 Lifecycle Policy page.

While October 2027 may seem distant, many businesses rely on SQL Server for critical applications such as ERP systems, accounting platforms, manufacturing software, healthcare applications, and custom business systems. These dependencies often require extensive testing before upgrades can occur.

What Happens After Support Ends?

End of support does not mean SQL Server 2017 will stop functioning on October 13, 2027.

The database platform will continue operating, but Microsoft will no longer provide security updates or product support.

Organizations that continue running SQL Server 2017 after support ends assume responsibility for managing risks associated with unsupported software. As vulnerabilities are discovered, fixes may no longer be available through standard support channels.

Microsoft offers several options to help organizations modernize, including upgrades to newer SQL Server versions and migration paths to Azure SQL services. More details are available in Microsoft's SQL Server End of Support Overview.

Risks of Staying on SQL Server 2017

Increased Security Exposure

Security updates are one of the primary reasons organizations maintain supported software.

Once SQL Server 2017 support ends, newly discovered vulnerabilities may remain unpatched. Unsupported systems can become difficult to align with cybersecurity frameworks, cyber insurance requirements, and internal security policies.

For organizations using Microsoft 365 security controls such as Microsoft Defender, Conditional Access, and identity-based security strategies, unsupported infrastructure can create gaps in an otherwise modern security environment.

Compliance and Audit Challenges

Many regulatory frameworks require organizations to maintain supported software and apply security updates in a timely manner.

Depending on the industry, running unsupported database platforms may create additional audit findings, remediation requirements, or documentation obligations.

Application Compatibility Concerns

Business-critical applications rarely operate in isolation.

As vendors continue supporting newer operating systems, databases, and integrations, organizations may encounter compatibility limitations with older SQL Server versions.

Delaying upgrades can increase project complexity as multiple technology components age simultaneously.

Higher Operational Costs

Older infrastructure often requires additional maintenance, troubleshooting, and support resources.

Organizations that proactively modernize typically gain access to improved performance, automation capabilities, and simplified lifecycle management.

Your Upgrade Options

There is no universal upgrade path. The best option depends on application requirements, compliance needs, internal resources, and long-term cloud strategy.

SQL Server 2025

For organizations that want to remain on-premises or maintain direct control over database infrastructure, SQL Server 2025 represents the latest supported version of Microsoft's database platform.

According to Microsoft, SQL Server 2025 introduces enhancements in performance, security, AI integration, and scalability while extending platform support for future planning.

Learn more in Microsoft's overview of What's New in SQL Server 2025.

Before upgrading, organizations should also review Microsoft's guidance for hardware and software requirements and supported upgrade paths.

Azure SQL Managed Instance

Azure SQL Managed Instance is often the most straightforward modernization path for organizations seeking high compatibility with existing SQL Server workloads while reducing infrastructure management responsibilities.

Microsoft manages patching, backups, and high availability, allowing IT teams to focus on business priorities rather than routine database maintenance.

Learn more about Azure SQL Managed Instance.

Azure SQL Database

Azure SQL Database is a fully managed Platform as a Service (PaaS) offering designed for cloud-native database workloads.

Organizations can reduce administrative overhead while benefiting from built-in resiliency, automated updates, and scalable infrastructure.

Microsoft provides a detailed comparison of Azure SQL deployment models in its Azure SQL feature comparison.

SQL Server on Azure Virtual Machines

Some organizations require full operating system and SQL Server control while still wanting cloud flexibility.

SQL Server on Azure Virtual Machines offers an Infrastructure as a Service (IaaS) approach that enables organizations to move existing workloads to Azure with fewer application changes.

Microsoft provides guidance on SQL deployment options in its overview of Azure SQL IaaS versus PaaS services.

Recommended Timeline

Waiting until 2027 to begin planning can significantly reduce available migration options and increase project risk.

A practical approach includes:

2026: Assessment and Discovery

• Inventory SQL Server instances
• Identify application dependencies
• Review licensing requirements
• Assess infrastructure health
• Evaluate cloud readiness

Early 2027: Design and Testing

• Select target platform
• Build migration plan
• Test application compatibility
• Validate performance requirements
• Create rollback procedures

Mid to Late 2027: Migration and Optimization

• Execute migration
• Validate application functionality
• Optimize performance
• Decommission legacy systems

Organizations considering Azure should also review Microsoft's migration guidance for SQL Managed Instance and resources from the Azure Cloud Adoption Framework.

Next Steps for Assessment

The most effective SQL Server 2017 end of support strategy begins with understanding your current environment.

A comprehensive assessment should identify:

• SQL Server versions and editions
• Business applications using SQL Server
• Infrastructure dependencies
• Security and compliance requirements
• Performance considerations
• Cloud readiness opportunities

For many SMBs, the decision is not simply whether to upgrade. It is whether SQL Server 2025, Azure SQL Managed Instance, Azure SQL Database, or SQL Server on Azure Virtual Machines best aligns with future business requirements.

Organizations that begin planning early gain greater flexibility, reduce project risk, and create a clearer path toward a secure and supportable database environment before SQL Server 2017 reaches end of support in October 2027.

FAQ

When does SQL Server 2017 reach end of support?

SQL Server 2017 reaches end of support on October 12, 2027. After that date, Microsoft will no longer provide security updates, non-security updates, or standard technical support.

Is SQL Server 2017 still supported?

Yes. SQL Server 2017 remains supported until October 12, 2027. Organizations should use this time to assess upgrade and migration options before support ends.

What happens after SQL Server 2017 support ends?

SQL Server 2017 will continue running, but Microsoft will no longer provide security updates or technical support. Organizations may face increased security, compliance, and operational risks over time.

Can I continue running SQL Server 2017 after end of support?

Yes. However, running unsupported software may increase risk exposure and complicate compliance requirements. Organizations should evaluate upgrade or migration options well before support ends.

Should I upgrade to SQL Server 2025 or move to Azure?

The answer depends on your business requirements. Organizations seeking maximum infrastructure control may prefer SQL Server 2025. Organizations looking to reduce management overhead and improve scalability often evaluate Azure SQL Managed Instance, Azure SQL Database, or SQL Server on Azure Virtual Machines.

How long does a SQL Server migration take?

Migration timelines vary based on application complexity, infrastructure dependencies, testing requirements, and data volume. Many SMB environments require several months for assessment, planning, testing, and implementation.