SQL Server 2017 EOS Checklist: 8 Steps to Prepare Before October 2027

SQL Server 2017 end of support is approaching, with Microsoft's support lifecycle ending on October 12, 2027. While that date may seem far away, organizations that rely on SQL Server for business-critical applications should begin planning well in advance.

A successful SQL Server upgrade or migration often involves more than updating database software. It requires understanding application dependencies, evaluating infrastructure, reviewing licensing, validating security requirements, and developing a migration strategy that minimizes operational disruption.

This SQL Server 2017 end of support checklist provides a practical framework for SMB executives, operations leaders, and IT decision-makers to prepare for modernization while reducing risk and maintaining business continuity.

According to Microsoft's SQL Server 2017 lifecycle policy, standard support ends on October 12, 2027. Organizations that start planning early typically have more flexibility in choosing the right upgrade or migration path.

Inventory SQL Instances

The first step in any SQL Server 2017 end of support project is understanding exactly what exists within the environment.

Many organizations discover multiple SQL Server instances that support departmental applications, reporting systems, vendor platforms, or legacy workloads.

Create a Complete SQL Inventory

Document:

• SQL Server versions and editions
• Server locations
• Database sizes
• Operating systems
• Business owners
• Application owners
• Backup and recovery processes

Identify Unsupported Infrastructure

During inventory, identify:

• End-of-life operating systems
• Legacy hardware
• Unsupported applications
• Databases with no documented owner

A complete inventory creates the foundation for every decision that follows.

Identify Application Dependencies

Many SQL Server environments support applications that have accumulated over years of business growth.

Before planning an upgrade, understand what depends on each SQL Server instance.

Map Business-Critical Applications

Identify:

• ERP systems
• Accounting platforms
• Manufacturing systems
• CRM applications
• Reporting platforms
• Custom applications
• Third-party software

Review Vendor Support Requirements

Some software vendors only support specific SQL Server versions.

Determine:

• Which applications support SQL Server 2025
• Which applications support Azure SQL services
• Whether application upgrades are required before database upgrades

This step helps prevent unexpected compatibility issues during migration.

Review Licensing

Licensing decisions can significantly influence modernization strategy.

Organizations should understand their current SQL Server licensing model before evaluating upgrade options.

Assess Current Licensing

Review:

• Core-based licensing
• Server and CAL licensing
• Software Assurance coverage
• Enterprise versus Standard Edition usage

Compare Future Licensing Options

Organizations evaluating SQL Server 2025 should review Microsoft's guidance on supported upgrade paths.

Organizations considering Azure should evaluate whether cloud-based licensing and consumption models align better with future operational requirements.

Assess Server Hardware

Not every SQL Server 2017 environment can be upgraded using existing infrastructure.

Older servers may not meet the requirements for newer database platforms.

Review Hardware Capacity

Evaluate:

• CPU utilization
• Memory utilization
• Storage performance
• Backup capacity
• Disaster recovery infrastructure

Validate SQL Server 2025 Requirements

Organizations planning an on-premises upgrade should review Microsoft's hardware and software requirements for SQL Server 2025.

Modernization projects often provide an opportunity to improve performance and simplify infrastructure management.

Evaluate Cloud Readiness

SQL Server 2017 end of support creates a natural opportunity to evaluate whether cloud-based database services support long-term business objectives.

Not every workload belongs in the cloud, but many organizations benefit from understanding available options before making infrastructure investments.

Evaluate Azure SQL Options

Microsoft offers several migration paths, including:

• SQL Server 2025 on-premises
• SQL Server on Azure Virtual Machines
• Azure SQL Managed Instance
• Azure SQL Database

Microsoft's overview of Azure SQL deployment models explains the differences between Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) approaches.

Consider Security and Operational Benefits

Cloud-based SQL services may help organizations:

• Reduce patch management responsibilities
• Improve resiliency
• Simplify backup management
• Increase scalability
• Improve disaster recovery capabilities

Organizations already leveraging Microsoft 365 and Microsoft Entra ID may also benefit from tighter integration between identity, access management, and cloud-hosted database services.

Test Upgrades

Testing is one of the most important phases of any SQL Server modernization effort.

Validate Application Compatibility

Test:

• Database functionality
• Application integrations
• Reporting systems
• Scheduled jobs
• Authentication workflows
• Backup and recovery procedures

Perform Performance Testing

Validate:

• Query performance
• Resource utilization
• Storage performance
• Application response times

Testing should occur in a controlled environment before production migration begins.

Plan Cutover

Migration planning reduces operational risk and helps ensure business continuity.

Establish a Migration Runbook

Document:

• Migration tasks
• Responsible stakeholders
• Communication plans
• Maintenance windows
• Validation procedures
• Escalation paths

Coordinate Business Stakeholders

Business leaders, application owners, and IT teams should understand:

• Planned downtime
• Expected impacts
• Testing requirements
• Success criteria

Clear communication helps reduce surprises during migration events.

Establish a Rollback Plan

Even well-tested migrations require contingency planning.

Define Rollback Criteria

Determine:

• What constitutes a successful migration
• Acceptable performance thresholds
• Validation requirements
• Decision points for rollback

Validate Recovery Procedures

Ensure:

• Backups are current
• Recovery processes are tested
• Recovery time objectives are documented
• Recovery point objectives are achievable

A documented rollback strategy helps organizations respond confidently if unexpected issues arise.

Building a SQL Server 2017 Modernization Roadmap

The most successful SQL Server modernization projects begin with preparation rather than urgency.

Organizations that complete this SQL Server 2017 end of support checklist gain a clearer understanding of:

• Current infrastructure
• Business dependencies
• Licensing considerations
• Security requirements
• Migration options
• Operational risks

Whether the destination is SQL Server 2025, Azure SQL Managed Instance, Azure SQL Database, or SQL Server on Azure Virtual Machines, a structured assessment process helps reduce risk and improve decision-making.

Microsoft also provides additional migration resources through its SQL Managed Instance migration guide and the Azure Cloud Adoption Framework.

The goal is not simply to complete an upgrade before SQL Server 2017 end of support. It is to ensure that business-critical database platforms remain secure, supportable, and aligned with future business requirements.

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 standard security updates, bug fixes, or technical support.

What should be included in a SQL Server 2017 end of support assessment?

A comprehensive assessment should include SQL instance inventory, application dependency mapping, licensing reviews, infrastructure evaluations, cloud readiness analysis, compatibility testing, migration planning, and rollback procedures.

Can I upgrade directly from SQL Server 2017 to SQL Server 2025?

Microsoft supports specific upgrade paths depending on your current version and edition. Organizations should review Microsoft's supported upgrade guidance and validate application compatibility before proceeding.

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

The best option depends on application requirements, compliance needs, operational goals, and cloud strategy. Organizations seeking reduced infrastructure management often evaluate Azure SQL services, while others may prefer maintaining on-premises control with SQL Server 2025.

How long does a SQL Server migration take?

Migration timelines vary based on database size, application complexity, testing requirements, and business dependencies. Many organizations begin planning 12–18 months before end of support to ensure adequate time for assessment and testing.

What are the risks of delaying SQL Server 2017 end of support planning?

Delaying planning can reduce migration options, compress testing timelines, increase project complexity, and create operational challenges as surrounding infrastructure and applications continue to evolve.