Time to Bail · Boarding pass
Check. You can stay.
From April 12, 2027 you cannot create SQL Server 2017 instances. Support ends October 13, 2027.[1]
Act means: change a setting or plan before the date. You can stay.
Cloud SQL for SQL Server 2017: no new instances from April 12, 2027
From April 12, 2027 you cannot create new Cloud SQL instances on SQL Server 2017. On October 13, 2027 Microsoft stops security updates and Cloud SQL stops supporting it.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
Tick steps as you go. Your progress stays in this browser.
In the console, filter Cloud SQL instances by database version.
Terraform, clones and test setups that create SQL Server 2017 instances stop working on April 12, 2027.
Test a newer SQL Server version on a copy, then upgrade before October 13, 2027.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
| No new instances from | April 12, 2027[1] |
|---|---|
| SQL Server version | 2017[1] |
| Editions | SQL Server 2017 Standard, Enterprise, Express and Web[1] |
| End of life | October 13, 2027: Microsoft stops security updates, and Cloud SQL stops supporting SQL Server 2017[1] |
| Extended support fee | Cloud SQL does not charge for extended support for SQL Server[1] |
| Newer versions | SQL Server 2019, 2022, 2025, as listed by Cloud SQL[1] |
| Instances on SQL Server 2017 | Keep running for now; support ends October 13, 2027[1] |
Check it yourself. Every fact above links here.
Time to bail on Cloud SQL for SQL Server 2017? Check. You can stay. From April 12, 2027 you cannot create SQL Server 2017 instances. Support ends October 13, 2027.
On our scale this is Act: change a setting or plan before the date. You can stay.
From April 12, 2027 you cannot create new Cloud SQL instances on SQL Server 2017. On October 13, 2027 Microsoft stops security updates and Cloud SQL stops supporting it.
Here are the facts we checked:
You can stay on Cloud SQL. You have to change a setting or plan before the date.
Leaving is a choice here, not a must.
Google Cloud is the main source for this page. Cloud SQL has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Instances on SQL Server 2017: Keep running for now; support ends October 13, 2027.
The date to remember is April 12, 2027. Make the change before then.
A few tips:
If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.
If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.
Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.
Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.
No questions collected yet.
Thanks.
Run SaaS spend at work? Get these changes before the invoice
Arrivals · for builders
People on Cloud SQL for SQL Server 2017 can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.
Listing is free. An editor checks it. Not ranked. Not paid.
One email when we publish a checked change in the category you pick. No account needed.
One email on Mondays: the gates in the next 14 days, with the first step for each.