Guide
SQL Server 2017 end of support: the planning guide
Microsoft’s extended support for SQL Server 2017 ends on October 12, 2027. After that date the product receives no security updates through standard support. You have three options: upgrade in place, buy time where Microsoft offers Extended Security Updates, or migrate the warehouse to a cloud platform. This guide compares them and gives a twelve-month plan that controls risk, validation and cost.
The dates
When does SQL Server 2017 support end?
| Version | Extended support ends | What it means |
|---|---|---|
| SQL Server 2016 | July 2026 (ended) | Microsoft lists Extended Security Updates running to July 2029 |
| SQL Server 2017 | October 12, 2027 | No security updates through standard support after this date |
| SQL Server 2019 | January 2030 | The next date in the SQL Server lifecycle |
Dates from Microsoft’s lifecycle pages. Check your own edition and licensing with Microsoft.
The options
What are the options before SQL Server 2017 support ends?
| Option | What changes | Risk | Fits when |
|---|---|---|---|
| Upgrade in place to a newer SQL Server | The engine version; the logic stays as it is | Low for the logic; compatibility testing needed | The platform is staying and the estate is healthy |
| Extended Security Updates, where offered | Nothing; you pay for security fixes | Cost rises each year; the deadline only moves | You need time to finish a move already planned |
| Move to a managed SQL Server service in the cloud | Where the engine runs; the logic stays T-SQL | Low to medium; SSIS and Agent jobs still need a home | You want off the hardware, not off SQL Server |
| Migrate the warehouse to Databricks, Fabric, Snowflake or BigQuery | The platform and the dialect; the logic is converted | Higher unless each object is proven | The business wants a lakehouse or AI workloads the old platform cannot serve |
The decision
Should you upgrade SQL Server or migrate the warehouse?
- Upgrade if the warehouse meets the business’s needs and the only problem is the support date.
- Migrate if a platform decision is already made, the license cost is the issue, or AI and analytics plans need a different platform.
- Do not let the date choose for you. An upgrade done in a hurry and a migration done later means paying twice.
- Either way, count the logic first. Stored procedures, SSIS packages and SQL Agent jobs decide the effort of both paths.
The plan
How do you plan a SQL Server 2017 migration in twelve months?
- Month 1: count the estate. Every procedure, function, view, SSIS package and SQL Agent job, with dead code flagged.
- Month 2: decide the target and fix the price from the count.
- Months 3 and 4: convert and prove one domain. This tests the method on your own code.
- Months 5 to 9: convert the remaining domains in parallel, reconciling each object against the original.
- Months 10 and 11: run old and new side by side, domain by domain, and cut over each one when it meets the agreed threshold.
- Month 12: retire the SQL Server 2017 instances, keeping the reconciliation reports as the audit record.
Risk
What goes wrong in SQL Server migrations, and how do you control it?
- Cursors, temp tables and dynamic SQL inside procedures behave differently on the target. Convert by rule and reconcile each one.
- SSIS packages and SQL Agent schedules carry business rules nobody documented. Inventory them before pricing.
- Case sensitivity changes results: T-SQL comparisons are case-insensitive by default, and Spark’s are not.
- The parallel run has no end date. Agree the pass threshold in writing before the first object converts.
With Novuz
How does Novuz help with SQL Server 2017 end of support?
The Novuz estate assessment counts every stored procedure, SSIS package and SQL Agent job in three business days for $3,000, lists the dead code and fixes the migration price. Novuz then converts the logic by fixed rules to Databricks, Microsoft Fabric, Snowflake, Google BigQuery, Apache Iceberg or Delta Lake, and reconciles every object against the original. A First Domain takes 5 to 6 weeks.
FAQ
Frequently asked questions
When does SQL Server 2017 reach end of support?
Microsoft’s extended support for SQL Server 2017 ends on October 12, 2027. After that date it receives no security updates through standard support.
What should we do before SQL Server 2017 end of support?
Count the logic first, then choose: upgrade in place, buy time with Extended Security Updates where Microsoft offers them, or migrate the warehouse to Databricks, Microsoft Fabric, Snowflake or BigQuery. Twelve months is enough to migrate if the first month is spent counting. Novuz converts the procedures, SSIS packages and Agent jobs and proves each one.
Is it better to upgrade SQL Server 2017 or migrate to the cloud?
Upgrade if the warehouse still serves the business and only the date is the problem. Migrate if the platform decision, the license cost or AI plans point elsewhere. Count the stored procedures and SSIS packages before deciding, because they set the effort of both.
Are Extended Security Updates available for SQL Server 2017?
Check with Microsoft for your edition and licensing. Extended Security Updates are paid security fixes beyond the end-of-support date, where Microsoft offers them. They move the deadline; they do not remove it.
How long does a SQL Server migration take?
It depends on the object count. With Novuz, the assessment takes three business days, a First Domain 5 to 6 weeks, and delivered estates of 1,000 to 1,600 objects typically 4 to 8 weeks.
Sources and further reading
Written by Ted Ghose, Co-founder and CTO, Novuz
Last reviewed:
Find out what your logic debt is costing you.
Every object counted, lineage, dead code and a fixed price in three business days. $3,000, credited.
Not sure which door? The scorecard takes ten minutes and tells you.