--- title: "SQL Server end of support dates by version | DB24" url: https://db24.ai/sql-server-support-dates description: "Microsoft's support dates for SQL Server 2012 to 2025, what out of support means in practice, and what to do: inventory, prioritise, upgrade." lang: en --- # Which SQL Server versions are out of support, and what should you do? Last updated 29 October 2026 ยท DB24 Team On 29 October 2026, SQL Server 2012, 2014 and 2016 are out of support, and SQL Server 2017 follows on 12 October 2027. Out of support means Microsoft releases no security updates for a version, except through Extended Security Updates (ESU) for 2014 and 2016, which Microsoft calls "a last resort paid option". Find every instance on those versions, rank them by exposure and business value, and plan each upgrade with a date. ## Key takeaways - SQL Server 2016 left extended support on 14 July 2026. SQL Server 2012 and 2014 left earlier, and ESU for SQL Server 2012 ended in July 2025. - SQL Server 2017 and 2019 are in extended support and receive security updates only. Support for SQL Server 2017 ends on 12 October 2027. - SQL Server 2022 and 2025 are in mainstream support. - SERVERPROPERTY returns the version and cumulative update of each instance. Compare the result with Microsoft's list of latest updates (KB321185) (https://support.microsoft.com/en-us/servicing/sql/kb321185-download-and-install-latest-updates). ## What are the support dates for each SQL Server version? Every version below follows Microsoft's Fixed Lifecycle Policy (https://learn.microsoft.com/en-us/lifecycle/policies/fixed): mainstream support with all updates, then extended support with security updates only. The dates come from each version's page on Microsoft Lifecycle (https://learn.microsoft.com/en-us/lifecycle/products/?products=sql-server), which shows them in US Pacific Time. | SQL Server version | Mainstream support ends | Extended support ends | Status on 29 October 2026 | | --- | --- | --- | --- | | SQL Server 2012 | 11 July 2017 | 12 July 2022 | Out of support. ESU ended 8 July 2025 | | SQL Server 2014 | 9 July 2019 | 9 July 2024 | Out of support. Security updates only through ESU, until July 2027 | | SQL Server 2016 | 13 July 2021 | 14 July 2026 | Out of support. Security updates only through ESU, until July 2029 | | SQL Server 2017 | 11 October 2022 | 12 October 2027 | Extended support: security updates only | | SQL Server 2019 | 28 February 2025 | 8 January 2030 | Extended support: security updates only | | SQL Server 2022 | 11 January 2028 | 11 January 2033 | Mainstream support | | SQL Server 2025 | 6 January 2031 | 6 January 2036 | Mainstream support | Last checked: 29 October 2026. This page is updated quarterly against Microsoft Lifecycle. ## What does "out of support" mean in practice? In Microsoft's update list, the newest cumulative update for SQL Server 2019 is CU32 from February 2025, the month mainstream support ended. Since then only security updates (GDRs) have followed. After extended support ends, Microsoft "doesn't provide patches or security updates" (SQL Server ESU FAQ (https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/extended-security-updates-frequently-asked-questions)). In October 2026, KB321185 lists security updates for SQL Server 2017, 2019, 2022 and 2025; the newest for SQL Server 2016 is from July 2026. The exception is ESU: - Only for SQL Server 2014 and 2016, Enterprise and Standard editions. For SQL Server 2012 and earlier, Microsoft's answer is to upgrade. - Security updates rated Critical by the Microsoft Security Response Center, if and when needed, for up to three years after extended support ends. No new features or other fixes. - Obtained through Azure Arc, an Azure VM or volume licensing (https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/sql-server-extended-security-updates). Microsoft describes ESU as "a temporary bridge to stay secure while one migrates to a newer, supported platform" (Lifecycle ESU FAQ (https://learn.microsoft.com/en-us/lifecycle/faq/extended-security-updates)). ## What about Windows Server? The operating system under SQL Server has its own dates on Microsoft Lifecycle: - **Windows Server 2012 and 2012 R2:** extended support ended on 10 October 2023, and the last ESU year ended on 13 October 2026. - **Windows Server 2016:** mainstream support ended on 11 January 2022; extended support ends on 12 January 2027. - **Windows Server 2019:** mainstream support ended on 9 January 2024; extended support ends on 9 January 2029. - **Windows Server 2022:** mainstream support ended on 13 October 2026; extended support ends on 14 October 2031. The host also limits the upgrade: SQL Server 2025 requires (https://learn.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2025) Windows Server 2019 or later. ## How do you find the version and patch level of every instance? On each instance: - **SERVERPROPERTY('ProductVersion')** returns the build as major.minor.build.revision. The major number gives the version: 11 is SQL Server 2012, 12 is 2014, 13 is 2016, 14 is 2017, 15 is 2019, 16 is 2022 and 17 is 2025. - **SERVERPROPERTY('ProductLevel')** returns RTM or the service pack, **ProductUpdateLevel** the cumulative update (CU n) and **ProductUpdateReference** the KB article for that release (SERVERPROPERTY (https://learn.microsoft.com/en-us/sql/t-sql/functions/serverproperty-transact-sql)). - **@@VERSION (https://learn.microsoft.com/en-us/sql/t-sql/functions/version-transact-sql-configuration-functions)** returns version, build, edition and operating system in one string. Compare each build with KB321185, Microsoft's list of the latest updates per version. Microsoft recommends "the latest Cumulative Update (or one released in the last year)". Across many instances, keep the results in one list and look for instances missing from it, such as test servers and SQL Server installed with an application. ## What should you do about instances that are out of support? 1. **Inventory.** List every instance with version, build, edition, host operating system, owner and the business system it supports. 2. **Prioritise by exposure and business value.** Start with out-of-support instances that hold critical data or are reachable from many systems, then those nearest their end date. 3. **Choose the upgrade path.** Microsoft calls an in-place upgrade (https://learn.microsoft.com/en-us/sql/database-engine/install-windows/choose-a-database-engine-upgrade-method) the easiest, with some downtime and a slower fallback. A migration to a new installation reduces risk and downtime and suits new hardware or a new operating system. Check the supported upgrade paths (https://learn.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2025) first. 4. **Keep the compatibility level at first.** Databases keep their compatibility level (https://learn.microsoft.com/en-us/sql/t-sql/statements/alter-database-transact-sql-compatibility-level) after an upgrade if the new version allows it. Microsoft calls that valid and recommends moving to the latest level later, in a controlled way. 5. **Use ESU only as a bridge** for SQL Server 2014 or 2016 that cannot be upgraded in time. 6. **Write down the plan and the date.** It is the evidence a supervisor or auditor is likely to ask for. Microsoft lists the options in SQL Server end of support options (https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/sql-server-end-of-support-overview). ## Does NIS2 require us to upgrade? The directive names no product, but in Sweden the regulations on security measures, MCFFS 2026:11 (https://www.ncsc.se/siteassets/radgivning-och-stod/foreskrifter/mcffs-2026-11-foreskrifter-och-allmanna-rad-om-sakerhetsatgarder-och-ledningens-utbildning-for-vasentliga-och-viktiga-verksamhetsutovare.pdf), have applied since 1 October 2026: security updates must be applied promptly, and software for which the supplier no longer provides security updates must be replaced or upgraded without undue delay (Chapter 4, Section 31). Security tests must check that systems run the latest approved version (Chapter 4, Section 27). In our reading, an instance on SQL Server 2012, or on 2014 or 2016 without ESU, falls under that rule. More in NIS2 and SQL Server (https://db24.ai/nis2-sql-server), and the wider task list in How to run SQL Server without a DBA (https://db24.ai/sql-server-without-a-dba). ## How DB24 helps DB24 shows the version and patch status of every instance in one place, so whoever owns SQL Server sees which instances are out of support or behind on updates: - **Lifecycle per instance:** version, edition, release date and whether Microsoft still supports it, with the end of mainstream support. - **Patch Advisor:** the installed patch and how long it has been live, the recommended target patch, and a link to Microsoft's documentation for it (release notes 2025.3 (https://db24.ai/docs/version-2025-3)). - **Current against Microsoft:** with Central Sync (https://db24.ai/docs/central-sync), SQL Server build and patch data is refreshed from DB24 Central, and the reports warn when it is more than two months old. No customer data leaves your environment in these checks. - **AiQ:** version lifecycle is scored in the Cost & Efficiency category, re-evaluated nightly, and a parameter below 10 becomes a recommendation listing every affected instance (AiQ (https://db24.ai/docs/aiq)). - **Your own reporting:** the same data is available in read-only SQL views (integration (https://db24.ai/docs/integration)). - **Help with the upgrade:** Data Platform Version Lift (https://db24.ai/services/data-platform-version-lift) is an expert service: inventory and compatibility assessment, an upgrade plan with a rollback strategy, the upgrade carried out by a senior SQL Server architect, and validation afterwards. DB24 is priced per SQL Server instance. Contact us for a quote. Installing cumulative and security updates stays with your team; DB24 shows where they are needed and keeps the record. To see it on your own instances, contact us (https://db24.ai/contact). ## Frequently asked questions ### When does support for SQL Server 2017 end? On 12 October 2027. Until then it receives security updates only. SQL Server 2022 and 2025 both accept an upgrade from SQL Server 2017. ### Can we still get security updates for SQL Server 2016? Only through Extended Security Updates, which Microsoft says are available until 17 July 2029. Express and Web editions are not eligible. ### Can we upgrade straight from SQL Server 2012 to SQL Server 2025? Not in place. SQL Server 2025 lists 2014 SP3, 2016 SP3, 2017 and 2019 as supported upgrade sources. SQL Server 2022 (https://learn.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2022) accepts SQL Server 2012 SP4. ### Is installing the latest cumulative update enough? For a version in support, it is what Microsoft recommends. For a version past its end date there are no new updates, except through ESU. ### How much does DB24 cost? ## Sources 1. Microsoft Lifecycle, Microsoft SQL Server 2012: https://learn.microsoft.com/en-us/lifecycle/products/microsoft-sql-server-2012 2. Microsoft Lifecycle, SQL Server 2014: https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2014 3. Microsoft Lifecycle, SQL Server 2016: https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2016 4. Microsoft Lifecycle, SQL Server 2017: https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2017 5. Microsoft Lifecycle, SQL Server 2019: https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2019 6. Microsoft Lifecycle, SQL Server 2022: https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2022 7. Microsoft Lifecycle, SQL Server 2025: https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2025 8. Microsoft Lifecycle, Windows Server 2012: https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2012 9. Microsoft Lifecycle, Windows Server 2012 R2: https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2012-r2 10. Microsoft Lifecycle, Windows Server 2016: https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2016 11. Microsoft Lifecycle, Windows Server 2019: https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2019 12. Microsoft Lifecycle, Windows Server 2022: https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2022 13. Microsoft Lifecycle, SQL Server products: https://learn.microsoft.com/en-us/lifecycle/products/?products=sql-server 14. Microsoft Lifecycle, Fixed Lifecycle Policy: https://learn.microsoft.com/en-us/lifecycle/policies/fixed 15. Microsoft Lifecycle, Extended Security Updates FAQ: https://learn.microsoft.com/en-us/lifecycle/faq/extended-security-updates 16. Microsoft Learn, What are Extended Security Updates for SQL Server?: https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/sql-server-extended-security-updates 17. Microsoft Learn, Extended Security Updates: frequently asked questions (SQL Server): https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/extended-security-updates-frequently-asked-questions 18. Microsoft Learn, SQL Server end of support options: https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/sql-server-end-of-support-overview 19. Microsoft Support, Latest updates and version history for SQL Server (KB321185): https://support.microsoft.com/en-us/servicing/sql/kb321185-download-and-install-latest-updates 20. Microsoft Learn, SERVERPROPERTY: https://learn.microsoft.com/en-us/sql/t-sql/functions/serverproperty-transact-sql 21. Microsoft Learn, @@VERSION: https://learn.microsoft.com/en-us/sql/t-sql/functions/version-transact-sql-configuration-functions 22. Microsoft Learn, Choose a Database Engine upgrade method: https://learn.microsoft.com/en-us/sql/database-engine/install-windows/choose-a-database-engine-upgrade-method 23. Microsoft Learn, Supported version and edition upgrades (SQL Server 2025): https://learn.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2025 24. Microsoft Learn, Supported version and edition upgrades (SQL Server 2022): https://learn.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2022 25. Microsoft Learn, SQL Server 2025 hardware and software requirements: https://learn.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2025 26. Microsoft Learn, ALTER DATABASE compatibility level: https://learn.microsoft.com/en-us/sql/t-sql/statements/alter-database-transact-sql-compatibility-level 27. MCFFS 2026:11, security measures and management training (PDF): https://www.ncsc.se/siteassets/radgivning-och-stod/foreskrifter/mcffs-2026-11-foreskrifter-och-allmanna-rad-om-sakerhetsatgarder-och-ledningens-utbildning-for-vasentliga-och-viktiga-verksamhetsutovare.pdf 28. DB24 Docs, Central Sync: https://db24.ai/docs/central-sync 29. DB24 Docs, Integration: https://db24.ai/docs/integration 30. DB24 Docs, AiQ: https://db24.ai/docs/aiq 31. DB24 Docs, Release notes 2025.3: https://db24.ai/docs/version-2025-3 32. DB24, Data Platform Version Lift: https://db24.ai/services/data-platform-version-lift ## Structured data ```json [ { "@context": "https://schema.org", "@type": "Organization", "name": "DB24", "url": "https://db24.ai", "logo": "https://db24.ai/logo.png", "description": "SQL Server on autopilot. DB24 monitors, backs up and documents SQL Server automatically for organisations that run it without a dedicated DBA.", "contactPoint": { "@type": "ContactPoint", "contactType": "sales", "email": "sales@db24.ai" }, "sameAs": [ "https://www.linkedin.com/company/db24" ] }, { "@context": "https://schema.org", "@type": "Article", "headline": "Which SQL Server versions are out of support, and what should you do?", "description": "Microsoft's support dates for SQL Server 2012 to 2025, what out of support means in practice, and what to do: inventory, prioritise, upgrade.", "datePublished": "2026-10-29", "dateModified": "2026-10-29", "inLanguage": "en", "author": { "@type": "Organization", "name": "DB24", "url": "https://db24.ai" }, "publisher": { "@type": "Organization", "name": "DB24", "logo": { "@type": "ImageObject", "url": "https://db24.ai/logo.png" } }, "image": [ "https://db24.ai/og-image.png" ], "mainEntityOfPage": { "@type": "WebPage", "@id": "https://db24.ai/sql-server-support-dates" } }, { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "When does support for SQL Server 2017 end?", "acceptedAnswer": { "@type": "Answer", "text": "On 12 October 2027. Until then it receives security updates only. SQL Server 2022 and 2025 both accept an upgrade from SQL Server 2017." } }, { "@type": "Question", "name": "Can we still get security updates for SQL Server 2016?", "acceptedAnswer": { "@type": "Answer", "text": "Only through Extended Security Updates, which Microsoft says are available until 17 July 2029. Express and Web editions are not eligible." } }, { "@type": "Question", "name": "Can we upgrade straight from SQL Server 2012 to SQL Server 2025?", "acceptedAnswer": { "@type": "Answer", "text": "Not in place. SQL Server 2025 lists 2014 SP3, 2016 SP3, 2017 and 2019 as supported upgrade sources. SQL Server 2022 accepts SQL Server 2012 SP4." } }, { "@type": "Question", "name": "Is installing the latest cumulative update enough?", "acceptedAnswer": { "@type": "Answer", "text": "For a version in support, it is what Microsoft recommends. For a version past its end date there are no new updates, except through ESU." } }, { "@type": "Question", "name": "How much does DB24 cost?", "acceptedAnswer": { "@type": "Answer", "text": "DB24 is priced per SQL Server instance. Contact us for a quote." } } ] }, { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://db24.ai/" }, { "@type": "ListItem", "position": 2, "name": "SQL Server support dates", "item": "https://db24.ai/sql-server-support-dates" } ] } ] ```