Microsoft JDBC Driver for SQL Server End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Microsoft JDBC Driver for SQL Server versions. Dates read at the vendor's own lifecycle pages (learn.microsoft.com). Updated at every deploy.
Microsoft JDBC Driver for SQL Server 13.6 is supported, with no end-of-life or end-of-support date announced yet. The next Microsoft JDBC Driver for SQL Server version to reach end of life is 10.2, on January 31, 2027. 13 of 23 tracked Microsoft JDBC Driver for SQL Server versions are past end of life; the most recent to reach it, 9.4, did so on July 30, 2026. The full Microsoft JDBC Driver for SQL Server lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 4.0 | — | — | Mar 6, 2017 | 3514 days past EOL | EOL |
| 4.1 | — | — | Dec 12, 2019 | 2503 days past EOL | EOL |
| 4.2 | — | — | Aug 24, 2020 | 2247 days past EOL | EOL |
| 6.0 | — | — | Jul 14, 2021 | 1923 days past EOL | EOL |
| 6.2 | 6.2.2 | Jun 30, 2017 | Jun 30, 2022 | 1572 days past EOL | EOL |
| 6.4 | 6.4.0 | Feb 27, 2018 | Feb 27, 2023 | 1330 days past EOL | EOL |
| 7.0 | 7.0.0 | Jul 31, 2018 | Jul 31, 2023 | 1176 days past EOL | EOL |
| 7.2 | 7.2.2 | Jan 31, 2019 | Jan 31, 2024 | 992 days past EOL | EOL |
| 7.4 | 7.4.1 | Jul 31, 2019 | Jul 31, 2024 | 810 days past EOL | EOL |
| 8.2 | 8.2.2 | Jan 31, 2020 | Jan 31, 2025 | 626 days past EOL | EOL |
| 8.4 | 8.4.1 | Jul 31, 2020 | Jul 31, 2025 | 445 days past EOL | EOL |
| 9.2 | 9.2.1 | Jan 29, 2021 | Jan 29, 2026 | 263 days past EOL | EOL |
| 9.4 | 9.4.1 | Aug 4, 2021 | Jul 30, 2026 | 81 days past EOL | EOL |
| 10.2 | 10.2.4 | Jan 31, 2022 | Jan 31, 2027 | 104 days remaining | Warning |
| 11.2 | 11.2.4 | Aug 9, 2022 | Aug 4, 2027 | 289 days remaining | Active |
| 12.2 | 12.2.1 | Jan 31, 2023 | Jan 31, 2028 | 469 days remaining | Active |
| 12.4 | 12.4.3 | Jul 31, 2023 | Jul 31, 2028 | 651 days remaining | Active |
| 12.6 | 12.6.5 | Feb 1, 2024 | Jan 31, 2029 | 835 days remaining | Active |
| 12.8 | 12.8.2 | Jul 31, 2024 | Jul 31, 2029 | 1016 days remaining | Active |
| 12.10 | 12.10.2 | Mar 17, 2025 | Jan 31, 2030 | 1200 days remaining | Active |
| 13.2 | 13.2.1 | Aug 15, 2025 | Mar 13, 2027 | 145 days remaining | Warning |
| 13.4 | 13.4.0 | Mar 13, 2026 | Sep 10, 2027 | 326 days remaining | Active |
| 13.6 | 13.6.1 | Sep 10, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/mssql-jdbc)
Microsoft JDBC Driver for SQL Server lifecycle status — the real story
The Microsoft JDBC Driver for SQL Server (Maven com.microsoft.sqlserver:mssql-jdbc) follows Microsoft's fixed lifecycle policy with mainstream support only: extended and custom support are not available for the driver. Drivers 12.x and older get five years of mainstream support per minor version. From 13.x, a major version is supported for at least five years, but each minor must be upgraded to the newest minor within 12 months of that newer minor's release to stay supported, so an older 13.x minor ends on its upgrade-by date. HeroDevs sells Never-Ending Support for the 10.2.x line.
Microsoft JDBC Driver for SQL Server release and support pattern
Across the 19 release lines with a published release date, Microsoft JDBC Driver for SQL Server has shipped a new line roughly every 6 months (median interval). A line typically stays supported for about 5 years from its release to its end-of-life date (measured on the 18 lines with both dates published).
Of the 23 release lines tracked, 13 are past end of life and 10 are still within support. The newest line, 13.6, was released September 10, 2026. The next scheduled end of life is 10.2 on January 31, 2027 — 103 days from this build. The longest-supported line currently published is 12.10, to January 31, 2030.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Microsoft JDBC Driver for SQL Server end of life mean for your organization?
When a version of Microsoft JDBC Driver for SQL Server reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Microsoft JDBC Driver for SQL Server should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Microsoft JDBC Driver for SQL Server reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your Microsoft JDBC Driver for SQL Server version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
Microsoft JDBC Driver for SQL Server has 13 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Microsoft JDBC Driver for SQL Server exists — vetted vendors ship security patches for years past the official date. Right now that coverage spans Microsoft JDBC Driver for SQL Server 10.2. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."