rss.livelink.threads-in-node

Announcing the release of Microsoft OLE DB Driver 19.4.2 for SQL Server

DavidLevy — Tue, 26 May 2026 17:12:48 GMT

We're pleased to announce the general availability (GA) release of Microsoft OLE DB Driver 19.4.2 for SQL Server. This is a maintenance update to the 19.4 line that improves TLS handling, raises a long-standing connection redirection limit, refreshes the bundled authentication library, and fixes accessibility issues in the UDL dialog.

Download

x64 / Arm64 installer
x86 installer

The 64-bit MSI continues to install the appropriate binary (x64 or Arm64) automatically based on the OS platform. MSOLEDBSQL 19 installs side by side with MSOLEDBSQL 18.

Prerequisite: the Microsoft Visual C++ Redistributable must be installed before running the driver installer.

What's new in 19.4.2

Features added

Feature	Details
SSL/TLS improvements	Improved SSL/TLS handling for better security and performance.
10 redirects per connection	The driver no longer caps connection redirections at 2, which removes a long-standing failure mode for workloads that hit redirection-heavy topologies (for example, certain Azure SQL routing scenarios).

Bugs fixed

Fix	Details
UDL accessibility defects	Fixed accessibility issues in the Universal Data Link (UDL) dialog.
Updated authentication library	Microsoft SQL Driver Authentication library (mssql-auth.dll) updated to version 1.1.3. mssql-auth.dll is the ADAL replacement introduced in 19.4.1 and is installed as part of the driver setup.

Supported languages

19.4.2 is available in: Chinese (Simplified), Chinese (Traditional), Czech, English (United States), French, German, Italian, Japanese, Korean, Polish, Portuguese (Brazil), Russian, Spanish, and Turkish. Direct per-language download links are available in the Release notes and the Download page.

Upgrading

If you're on 19.4.1 or earlier in the 19.x line, an in-place upgrade is supported. As always, we recommend validating in a non-production environment first, especially if your application depends on the redirection or TLS behaviors touched in this release.

Feedback

Please file issues and feature requests on the Microsoft OLE DB Driver for SQL Server feedback site or via your usual support channel. Thanks to everyone who reported the UDL accessibility and redirection-limit issues that drove this release.

Announcing mssql-django 1.7.2

DavidLevy — Fri, 22 May 2026 17:00:00 GMT

We're pleased to announce the release of mssql-django 1.7.2, a patch release that ships three targeted bug fixes for the Django backend for Microsoft SQL Server and Azure SQL. This release focuses on correctness: timezone-aware datetimes, QuerySet.explain() on Django 4.0+, and exception handling in a test utility.

Install or upgrade from PyPI:

pip install --upgrade mssql-django

What's new in 1.7.2

Correct timezone handling for DATETIMEOFFSET and Now() under USE_TZ=True

Two long-standing timezone issues are fixed in this release:

handle_datetimeoffset now parses the timezone offset from SQL Server's binary DATETIMEOFFSET representation. Previously, values read from DATETIMEOFFSET columns could be returned without their offset, leading to naive datetimes or values converted using the wrong zone. The backend now returns properly timezone-aware datetime objects.
Now() emits SYSDATETIMEOFFSET() when USE_TZ=True. When Django is configured with USE_TZ=True, the expression Now() previously compiled to SYSDATETIME(), which returns the SQL Server host's local time without offset information. On non-UTC hosts this produced timestamps that were silently shifted. With this fix, Now() compiles to SYSDATETIMEOFFSET() under USE_TZ=True and continues to compile to SYSDATETIME() when USE_TZ=False, matching Django's expectations.

The release adds regression tests covering UTC, +05:30 (IST), -05:00 (EST), -09:30 (Marquesas), and +05:45 (Nepal) offsets, plus a new NowSQLTemplateTests that pins the SQL template emitted in each USE_TZ mode.

QuerySet.explain() no longer raises AttributeError on Django 4.0+

In Django 4.0 the internal API for EXPLAIN plans changed: query.explain_format and query.explain_options were replaced by a single query.explain_info object. The mssql-django compiler still read the old attributes, which raised AttributeError whenever an application called .explain() on a queryset.

The compiler now reads the correct attribute based on the running Django version, so .explain() works again on Django 4.0, 4.1, 4.2, 5.0, 5.1, 5.2, and 6.0. A new ExplainRegressionTests suite locks in the behavior.

Test utility no longer swallows exceptions in finally

A return statement inside a finally block in the JSONField support probe (_check_jsonfield_supported_sqlite()) was silently swallowing exceptions, including KeyboardInterrupt and other BaseException subclasses. The return has been removed so exceptions propagate as Python intends.

Compatibility

mssql-django 1.7.2 supports:

Django: 3.2, 4.0, 4.1, 4.2, 5.0, 5.1, 5.2, 6.0
Python: 3.8 through 3.14
SQL Server: 2017, 2019, 2022, 2025; Azure SQL Database; Azure SQL Managed Instance
ODBC Driver: 17 or 18 for SQL Server (driver 18 is the default since 1.7, with automatic fallback to 17 when 18 is not installed)

No configuration changes are required to pick up the fixes in 1.7.2. Upgrade in place:

pip install --upgrade mssql-django

Upgrading from 1.7.1

1.7.2 is a drop-in replacement for 1.7.1. If your application:

reads from DATETIMEOFFSET columns,
uses django.db.models.functions.Now() with USE_TZ=True, or
calls QuerySet.explain() on Django 4.0+,

you will see corrected behavior after upgrading. Applications that previously worked around the timezone offset issue (for example by manually attaching tzinfo to values read from DATETIMEOFFSET columns) should review those workarounds; values returned by the ORM are now timezone-aware by default.

Thank you

Thanks to everyone who reported the underlying issues, contributed reproductions and test cases. Bug reports and pull requests are always welcome on GitHub.

mssql-python 1.7.1 and the case of the missing megabytes

DavidLevy — Thu, 21 May 2026 17:00:00 GMT

We just shipped mssql-python 1.7.1 to PyPI. This release is mostly polish, but the road to publishing it was bumpier than expected, and there is some housekeeping on the PyPI side worth talking about.

What's in 1.7.1

A handful of correctness, performance, and platform fixes that landed since 1.6.0:

PERF: UTF-16 string handling now goes through simdutf and std::u16string, cutting overhead on every string round-trip between Python and the driver.
PERF: Faster execute() hot path with soft reset, prepare caching, and guarded diagnostics.
FIX: Login failures now raise a proper mssql_python exception instead of a raw RuntimeError (issue #532).
FIX: Released the GIL around blocking SQLSetConnectAttr calls so that in-process SSH tunnels (paramiko + sshtunnel) no longer hang connect().
FIX: executemany no longer raises a RuntimeError when decimal signs change between rows (issue #557).
FIX: Consistent retrieval of CP1252-encoded data in VARCHAR columns across Windows and Linux (issue #468).
FIX: manylinux_2_28 build targets so RHEL 8 / glibc 2.28 users get wheels out of the box.
FIX: macOS Python 3.10 now gets a proper universal2 wheel.
DOC: Setup instructions for Azure Linux.

Full set of changes is in the 1.7.1 PR.

The PyPI space story

This release also forced us to confront something we've been watching for a while: we ran out of room on PyPI.

mssql-python ships native code with bundled ODBC driver binaries for every supported OS / architecture / Python version combination. Each wheel is sizeable on its own, and the number of combinations grows quickly: Windows x64 / ARM64 / x86, macOS universal2, manylinux x86_64 / aarch64, musllinux x86_64 / aarch64, across multiple Python versions. Multiply that by every release we keep on PyPI and the project size adds up fast.

PyPI projects have a per-project storage quota. When we tried to release 1.7.0 we hit it.

What we did short-term

To get 1.7.1 published we cleaned house on old artifacts that nobody should be pulling in fresh installs anymore:

Removed all 1.0.0-alpha packages from PyPI.
Removed all 1.x.x-beta packages from PyPI.
Removed the 1.7.0 packages that made it to PyPI before we hit the space limit.

Pre-release alphas and betas were intentionally there for early adopters during the ramp-up of the driver. None of them are recommended for production use, and the GA versions (1.0.0 and up) supersede everything those wheels offered. If you were pinned to an alpha or beta version, please move to the latest GA release (pip install -U mssql-python). If you have a specific reason that you can't, please let us know in an issue. We want to hear about it.

What we're doing longer-term

Cleaning out old pre-releases buys us breathing room, not a solution. The wheel matrix is going to keep growing as we add platforms, and we don't want to be back in the same spot in three releases.

We're attacking the problem from two directions in parallel:

Split up the deployment. We're working out how to break the published artifacts into smaller pieces so that an install only pulls down what it actually needs. Concretely we're evaluating splitting the bundled native dependencies (ODBC driver binaries, etc.) out of the main wheels so the per-platform wheel size drops substantially. Exact shape is still being designed and we'll have more to share when we've nailed it down. The goal is that a typical pip install mssql-python stays a one-liner with no extra steps, while the on-disk and on-PyPI footprint is a fraction of what it is today.
Asked PyPI for more space. In parallel we've put in a request to PyPI for a storage quota increase. This is a normal process for projects that legitimately need more room, and it gives us a safety net while the longer-term splitting work lands.

We are looking at the space increase as the immediate buffer, and the split is the durable fix.

Upgrading

Nothing user-visible has changed about how you install or use the driver:

pip install -U mssql-python

If you previously pinned to an alpha or beta version, you'll need to move to the latest GA. If you hit any issues during the upgrade, please file a GitHub issue — we read all of them.

Thanks

Thanks to everyone who filed bug reports, repro scripts, and PRs that fed into this release. The fixes we shipped came from real user issues, and the SSH-tunnel and CP1252 ones in particular were caught by community reproductions that made the root cause obvious. Keep them coming.

SQL Server 2025 Express - service starts with delay of some hours after restart of computer

mniederer — Thu, 21 May 2026 14:31:01 GMT

Dear Community,

we started using SQL Server 2025 Express but experienced problems with the start of service at startup.

When the computer is restarted, the service is not started. I observed this on nearly all installations and in one case it took kinda exactly 2 hours to start the service (or it was somehow delayed but without any trace in settings or windows logs).

When we start the service manually or by batch script it is starting properly at startup ...

What exactly causes this?

We only have this issue with 2025 Express and i have not yet found similar cases in the internet.

Thank you,

kind regards

Failure to run SSMS

oneeyeman1 — Wed, 20 May 2026 23:30:12 GMT

Hi, ALL,

For sometime I had both MSVC 2010 and 2017 installed on my laptop.

Recently I needed space and decided to remove the old version.

Unfortunately I thin I killed one of the SSMS libraries, because while it successfully starts, trying to go to the "New Query" window, Im getting the error "Library not registered".

The server itself operates just fine as I can connect to it.

Is there anyway to make it work again?

Than you.

Cumulative Update #5 for SQL Server 2025 RTM

HarveyMoraSQL — Tue, 26 May 2026 23:59:29 GMT

The 5th cumulative update release for SQL Server 2025 RTM is now available for download at the Microsoft Downloads site. Please note that registration is no longer required to download Cumulative updates.
To learn more about the release or servicing model, please visit:

CU5 KB Article: https://learn.microsoft.com/troubleshoot/sql/releases/sqlserver-2025/cumulativeupdate5

Starting with SQL Server 2017, we adopted a new modern servicing model. Please refer to our blog for more details on Modern Servicing Model for SQL Server.

Microsoft® SQL Server® 2025 RTM Latest Cumulative Update: https://www.microsoft.com/download/details.aspx?familyid=69e0b8fc-1c50-41bd-a576-b9c66b2f302a
Update Center for Microsoft SQL Server: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates

Cumulative Update #25 for SQL Server 2022 RTM

SrinivasSQL — Wed, 20 May 2026 19:59:45 GMT

The 25th cumulative update release for SQL Server 2022 RTM is now available for download at the Microsoft Downloads site. Please note that registration is no longer required to download Cumulative updates.
To learn more about the release or servicing model, please visit:

CU25 KB Article: https://learn.microsoft.com/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate25

Starting with SQL Server 2017, we adopted a new modern servicing model. Please refer to our blog for more details on Modern Servicing Model for SQL Server

Microsoft® SQL Server® 2022 RTM Latest Cumulative Update: https://www.microsoft.com/download/details.aspx?familyid=105013
Update Center for Microsoft SQL Server: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates

Security Update for SQL Server 2025 RTM CU4

SrinivasSQL — Tue, 26 May 2026 22:13:35 GMT

The Security Update for SQL Server 2025 RTM CU4 is now available for download at the Microsoft Download Center and Microsoft Update Catalog sites. This package cumulatively includes all previous security fixes for SQL Server 2025 RTM CUs, plus it includes the new security fixes detailed in the KB Article.

Security Bulletins:

CVE-2026-40370 - Security Update Guide - Microsoft - SQL Server Remote Code Execution Vulnerability

Security Update of SQL Server 2025 RTM CU4 KB Article: KB5089899
Microsoft Download Center: https://www.microsoft.com/download/details.aspx?familyid=a9274560-fbdb-421c-b2cb-123ab69dc098
Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Search.aspx?q=5089899
Latest Updates for Microsoft SQL Server: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates

Security Update for SQL Server 2025 RTM

SrinivasSQL — Tue, 26 May 2026 22:15:31 GMT

The Security Update for SQL Server 2025 RTM GDR is now available for download at the Microsoft Download Center and Microsoft Update Catalog sites. This package cumulatively includes all previous security fixes for SQL Server 2025 RTM, plus it includes the new security fixes detailed in the KB Article.

Security Bulletins:

CVE-2026-40370 - Security Update Guide - Microsoft - SQL Server Remote Code Execution Vulnerability

Security Update of SQL Server 2025 RTM GDR KB Article: KB5091223
Microsoft Download Center: https://www.microsoft.com/download/details.aspx?familyid=070dacdf-e60d-4a91-8e94-e1f4e453b7b5
Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Search.aspx?q=5091223
Latest Updates for Microsoft SQL Server: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates

Security Update for SQL Server 2022 RTM CU24

SrinivasSQL — Tue, 26 May 2026 22:13:00 GMT

The Security Update for SQL Server 2022 RTM CU24 is now available for download at the Microsoft Download Center and Microsoft Update Catalog sites. This package cumulatively includes all previous security fixes for SQL Server 2022 RTM CUs, plus it includes the new security fixes detailed in the KB Article.

Security Bulletins:

CVE-2026-40370 - Security Update Guide - Microsoft - SQL Server Remote Code Execution Vulnerability

Security Update of SQL Server 2022 RTM CU24 KB Article: KB5089900
Microsoft Download Center: https://www.microsoft.com/download/details.aspx?familyid=34ec989d-5c02-41b7-99ec-f2c35c7a4cdf
Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Search.aspx?q=5089900
Latest Updates for Microsoft SQL Server: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates

Security Update for SQL Server 2022 RTM

SrinivasSQL — Tue, 26 May 2026 22:15:48 GMT

The Security Update for SQL Server 2022 RTM GDR is now available for download at the Microsoft Download Center and Microsoft Update Catalog sites. This package cumulatively includes all previous security fixes for SQL Server 2022 RTM, plus it includes the new security fixes detailed in the KB Article.

Security Bulletins:

CVE-2026-40370 - Security Update Guide - Microsoft - SQL Server Remote Code Execution Vulnerability

Security Update of SQL Server 2022 RTM GDR KB Article: KB5091158
Microsoft Download Center: https://www.microsoft.com/download/details.aspx?familyid=9edbb614-c56a-4c5a-b4dc-157d4036f44c
Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Search.aspx?q=5091158
Latest Updates for Microsoft SQL Server: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates

Security Update for SQL Server 2019 RTM CU32

SrinivasSQL — Tue, 26 May 2026 22:16:05 GMT

The Security Update for SQL Server 2019 RTM CU32 is now available for download at the Microsoft Download Center and Microsoft Update Catalog sites. This package cumulatively includes all previous security fixes for SQL Server 2019 RTM CUs, plus it includes the new security fixes detailed in the KB Article.

Security Bulletins:

CVE-2026-40370 - Security Update Guide - Microsoft - SQL Server Remote Code Execution Vulnerability

Security Update of SQL Server 2019 RTM CU32 KB Article: KB5090407
Microsoft Download Center: https://www.microsoft.com/download/details.aspx?familyid=bb9b5d10-84c4-4cca-85bf-abb93a453f57
Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Search.aspx?q=5090407
Latest Updates for Microsoft SQL Server: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates

Security Update for SQL Server 2019 RTM

SrinivasSQL — Tue, 26 May 2026 22:16:32 GMT

The Security Update for SQL Server 2019 RTM GDR is now available for download at the Microsoft Download Center and Microsoft Update Catalog sites. This package cumulatively includes all previous security fixes for SQL Server 2019 RTM, plus it includes the new security fixes detailed in the KB Article.

Security Bulletins:

CVE-2026-40370 - Security Update Guide - Microsoft - SQL Server Remote Code Execution Vulnerability

Security Update of SQL Server 2019 RTM GDR KB Article: KB5090408
Microsoft Download Center: https://www.microsoft.com/download/details.aspx?familyid=ad8a836a-cf79-44c9-b361-d94a8fe698e1
Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Search.aspx?q=5090408
Latest Updates for Microsoft SQL Server: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates

Security Update for SQL Server 2017 RTM CU31

SrinivasSQL — Tue, 26 May 2026 22:16:51 GMT

The Security Update for SQL Server 2017 RTM CU31 is now available for download at the Microsoft Download Center and Microsoft Update Catalog sites. This package cumulatively includes all previous security fixes for SQL Server 2017 RTM CUs, plus it includes the new security fixes detailed in the KB Article.

Security Bulletins:

CVE-2026-40370 - Security Update Guide - Microsoft - SQL Server Remote Code Execution Vulnerability

Security Update of SQL Server 2017 RTM CU31 KB Article: KB5090354
Microsoft Download Center: https://www.microsoft.com/download/details.aspx?familyid=3d1a0db7-cdd3-4021-be11-73f43c870fac
Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Search.aspx?q=5090354
Latest Updates for Microsoft SQL Server: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates

Security Update for SQL Server 2017 RTM

SrinivasSQL — Tue, 26 May 2026 22:17:10 GMT

The Security Update for SQL Server 2017 RTM GDR is now available for download at the Microsoft Download Center and Microsoft Update Catalog sites. This package cumulatively includes all previous security fixes for SQL Server 2017 RTM, plus it includes the new security fixes detailed in the KB Article.

Security Bulletins:

CVE-2026-40370 - Security Update Guide - Microsoft - SQL Server Remote Code Execution Vulnerability

Security Update of SQL Server 2017 RTM GDR KB Article: KB5090347
Microsoft Download Center: https://www.microsoft.com/download/details.aspx?familyid=09c81e42-2942-4fb8-b84b-f0905fcd3b33
Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Search.aspx?q=5090347
Latest Updates for Microsoft SQL Server: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates

Security Update for SQL Server 2016 SP3 Azure Connect Feature Pack

SrinivasSQL — Tue, 26 May 2026 22:20:12 GMT

The Security Update for SQL Server 2016 SP3 Azure Connect Feature Pack is now available for download at the Microsoft Download Center and Microsoft Update Catalog sites. This package cumulatively includes all previous security fixes for SQL Server 2016 SP3 Azure Connect Feature Pack, plus it includes the new security fixes detailed in the KB Article.

Security Bulletins:

CVE-2026-40370 - Security Update Guide - Microsoft - SQL Server Remote Code Execution Vulnerability

Security Update of SQL Server 2016 SP3 Azure Connect Feature Pack KB Article: KB5089270
Microsoft Download Center: https://www.microsoft.com/download/details.aspx?familyid=f9014a03-feca-41c1-bc64-fb801e0e9799
Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Search.aspx?q=5089270
Latest Updates for Microsoft SQL Server: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates

Security Update for SQL Server 2016 SP3

SrinivasSQL — Tue, 26 May 2026 22:20:27 GMT

The Security Update for SQL Server 2016 SP3 GDR is now available for download at the Microsoft Download Center and Microsoft Update Catalog sites. This package cumulatively includes all previous security fixes for SQL Server 2016 SP3, plus it includes the new security fixes detailed in the KB Article.

Security Bulletins:

CVE-2026-40370 - Security Update Guide - Microsoft - SQL Server Remote Code Execution Vulnerability

Security Update of SQL Server 2016 SP3 GDR KB Article: KB5089271
Microsoft Download Center: https://www.microsoft.com/download/details.aspx?familyid=07b113c3-1315-444e-b442-b0297f0cebe1
Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Search.aspx?q=5089271
Latest Updates for Microsoft SQL Server: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates

Announcing SQL Server Management Studio 22.6.0

mbarickman — Tue, 12 May 2026 21:55:41 GMT

It's been a minute since I've posted here - but rest assured that the SSMS team has been working hard to bring you lots of exciting features and fixes! Today we shipped SQL Server Management Studio (SSMS) 22.6.0, and it's a really nice mix of work: continued investment in Database DevOps (preview), a security-related update to how we authenticate against Azure Storage, a handful of quality-of-life improvements in the editor and tools, and a solid roundup of bug fixes (many of which came directly from items filed on the feedback site!). Thank you, as always, for taking the time to log issues and upvote what matters to you. It really does shape what we work on.

Let's dig into what's new!

Database DevOps (preview)

SQL projects support in SSMS continues to evolve with incremental changes, including an adjustment to the Solution Explorer icon for solutions to match the '.slnx' icon found in Visual Studio.

SSMS Solution Explorer with the updated solutions icon.

This release also introduces the ability to create a SQL project directly from an existing database. Once a project is created, you can check it into source control and work with it in VS Code or vice versa, enabling a flexible experience across different tools and teams. If a database changes over time, you can use the SQL projects "Import From Database..." menu item in Solution explorer to update your project with the latest schema changes. This allows you to keep your project in sync with the database and maintain a single source of truth for your database schema.

New entry point alert! Now you can right click a database in Object Explorer and create a project from there!

Once your database definition is captured in a SQL project, CI/CD pipelines and the SqlPackage CLI can be used to automate deployments and manage the quality of database changes. Documentation is available at aka.ms/sqlprojects-docs, and our public roadmap at aka.ms/sqlprojects-roadmap shows what's coming next.

Unified Settings

We're continuing to migrate settings from the classic Tools > Options dialog into the new Unified Settings experience. In 22.6, Transact-SQL IntelliSense and Keyboard Query Shortcuts are now available in Unified Settings. If you haven't opened Unified Settings yet, give it a try. The search and filtering experience is significantly better than what we had before, and we'd love your feedback as we keep moving more settings over. I also recorded a Data Exposed episode with Anna Hoffman where I talk about a few ways you can customize your SSMS 22 installation to work for you.

The new Unified Settings experience is an embedded tab with powerful searching and filtering capabilities.

Storage Account access - now with Entra authentication

This one is worth calling out for anyone who connects to Azure Storage accounts from SSMS. The Storage Browser, DACPAC import/export, and Merge Audit File dialogs have all been updated to support Microsoft Entra-based authentication instead of shared key access. Shared keys have been a long-standing concern from a security perspective, and moving these flows to Entra brings them in line with modern authentication guidance.

Quality-of-life improvements

A few smaller changes that I think are worth highlighting:

Registered Servers: Multi-server connection attempts can now be cancelled. If you've ever kicked off a connection to a large group and immediately realized you picked the wrong one, you no longer have to wait it out. There's now a Cancel button.
Results Grid: Hovering over a column header in the results grid now shows the column's data type in the tooltip. Small, but handy, this comes straight from a feedback item.
Query Designer: In the Show Criteria pane, there's a new right-click option to Change Column Width for an individual column.

GitHub Copilot in SSMS

On the GitHub Copilot side, this release is primarily about stability and cleanup rather than new capabilities. We fixed a crash that some of you ran into when using Copilot Edit, and we removed the GPT-5* models from Ask mode. They may return down the road; for now, the remaining models should give you a more consistent experience.

If you missed Erin's blog post about 22.5.2, code completions are still disabled by default. You can opt back in under Tools > Options > Text Editor > Inline Suggestions.

Fixes worth highlighting

The full list is in the release notes, but a few that I expect folks will be happy to see:

Connection Dialog: Passwords are no longer displayed in plain text when viewing a connection string. This came in as a feedback item for SQL Lakehouse connections specifically, but the fix applies broadly.
Object Explorer: Fixed the "object reference not set to an instance of an object" error that some of you saw when deleting multiple items at once and addressed an issue where newly created objects sometimes didn't appear in Object Explorer until you disconnected and reconnected.
Migration Landing Page: the Migration page we introduced in 22.5 now supports dark theme!
Query Editor: Editor tooltips are no longer unreadable when you're using a dark theme with a light editor appearance.

A reminder on rolling back

We say this from time to time, but it's worth repeating: if a release ever creates trouble for you, you can roll back to a previous version of SSMS 22 from the Visual Studio Installer. From the SSMS 22 entry, select More > Rollback to previous version. And if you're ever in a spot where you need a specific older build, the Release History page lists them.

Summary

You can find the complete release notes here. As always, thank you for using SSMS, for the feedback items, the upvotes, the comments, and the patience as we keep iterating. Please keep them coming, the feedback site is the best way to influence what shows up in the next release.

A bizarre situation - SQL query finds no records when record is present.

Kevmeister6868 — Wed, 06 May 2026 03:15:21 GMT

I am trying to troubleshoot a bizarre situation, and looking for either an explanation of the cause, or assistance in determining the cause. The situation is esoteric (to say the least), so I'll need to paint a picture.

I am using SQL 2019 Enterprise for testing.

Our database has Allow Snapshot Isolation set to true, and the Is Read Committed Snapshot On is also true.

We have a table called T_App_View, with essentially these important fields (plus some audit fields not shown):

CREATE TABLE T_App_View ( C_Id int not null, C_Type varchar( 20 ) not null, C_Entity varchar( 250 ) not null, C_Specialisation varchar( 250 ) null, CONSTRAINT APPVIEW_PKC PRIMARY KEY NONCLUSTERED( C_Id ) )

We have an index on (Type, Entity, Specialisation):

create unique index APPVIEW_I01 on T_App_View( C_Type, C_Entity, C_Specialisation )

And from a historical hangover we have a view against the table that is used for queries:

CREATE VIEW dbo.VS_App_View AS SELECT * FROM dbo.T_App_View WITH CHECK OPTION

The table is used to define "UI views" for our application, and contains about 1000 records.

As part of commissioning a new database, we use a tool to load data into this table, and then the data basically sits there unchanged. Each time the tool is run it deletes any old data in the table, before populating the new data.

The tool deletes the old data row-by-row rather than using a truncate table statement or similar.

When our web tier is asked to provide the "definition" of a view, it performs a query on VS_App_View using the three compound key components of Type, Entity, and Specialisation. A dynamic cursor is used (a historical hangover from many years ago). A typical query would look similar to this:

SELECT appview.C_Id, appview.C_Entity_Id, appview.C_Specialisation, appview.C_View_Type FROM dbo.VS_App_View appview WHERE appview.C_View_Type = 'DETAIL' AND appview.C_Entity_Id = 'a' AND appview.C_Specialisation = 'Finance'

We are using the standard isolation level of Read Committed (which means Read Committed Snapshot in reality). Notice the select statement is not using an option of READCOMMITTED in the query.

The fun part

Sometimes when we do a lookup in SQL Server, the above query finds no matching records. This bug is very evasive, we cannot reproduce it, and it appears maybe once or twice a month, and other months not at all. It is not limited to specific key values, it just appears to happen randomly (or the pattern is obscure enough that we cannot yet see it).

Our QA team experienced the find failure the other day and one of our developers jumped into SSMS and ran the query manually and sure enough it came back with no records found. And now the bizarre bit:

The developer ran the query directly against the T_App_View table, and the record appeared. He then re-ran the query against the View, and the record appeared.

We have the Query Store enabled for this database and I can see two plans matching the above query (one for a null specialisation, and one for a non-null specialisation). The query plans look odd (due to the dynamic cursor presumably) because even though the index guarantees a maximum of one matching record, the query plan still shows a temporary table being constructed along with a clustered index for that table.

I feel like I am reasonably proficient in SQL Server but this one has me stumped. ChatGpt suggested it is a query plan issue, but I'm skeptical as I've never heard of a query plan not finding a record. I've only experienced query plan issues in terms of performance impacts.

Has anyone ever come across such a situation? Is Snapshot Isolation part of the problem here, or database statistics, or the fact we are deleting an entire table of records individually and then repopulating them (resulting in bad statistics)? Should we have used WITH( READCOMMITTEDLOCK ) for this query perhaps? Any suggestions on how to troubleshoot effectively, as in what to look at and for?

Thanks in advance for any help.

SSRS Report chart labels overlapping

Kalpesh27 — Tue, 05 May 2026 12:09:14 GMT

Hello Guys, I am new to SSRS report and we have implemented a report in which we are taking Survey response of current and past 2 years for specific set of questions and in some case the percentages are getting overlapped as per below screenshot.

We have tried few options as below, but it is not approved by client. Can someone please help me to resolve this issue?

rss.livelink.threads-in-node

Announcing the release of Microsoft OLE DB Driver 19.4.2 for SQL Server

Download

What's new in 19.4.2

Features added

Bugs fixed

Supported languages

Upgrading

Feedback

Announcing mssql-django 1.7.2

What's new in 1.7.2

Correct timezone handling for DATETIMEOFFSET and Now() under USE_TZ=True

QuerySet.explain() no longer raises AttributeError on Django 4.0+

Test utility no longer swallows exceptions in finally

Compatibility

Upgrading from 1.7.1

Thank you

Links

mssql-python 1.7.1 and the case of the missing megabytes

What's in 1.7.1

The PyPI space story

What we did short-term

What we're doing longer-term

Upgrading

Thanks

SQL Server 2025 Express - service starts with delay of some hours after restart of computer

Failure to run SSMS

Cumulative Update #5 for SQL Server 2025 RTM

Cumulative Update #25 for SQL Server 2022 RTM

Security Update for SQL Server 2025 RTM CU4

Security Update for SQL Server 2025 RTM

Security Update for SQL Server 2022 RTM CU24

Security Update for SQL Server 2022 RTM

Security Update for SQL Server 2019 RTM CU32

Security Update for SQL Server 2019 RTM

Security Update for SQL Server 2017 RTM CU31

Security Update for SQL Server 2017 RTM

Security Update for SQL Server 2016 SP3 Azure Connect Feature Pack

Security Update for SQL Server 2016 SP3

Announcing SQL Server Management Studio 22.6.0

Database DevOps (preview)

Unified Settings

Storage Account access - now with Entra authentication

Quality-of-life improvements

GitHub Copilot in SSMS

Fixes worth highlighting

A reminder on rolling back

Summary

A bizarre situation - SQL query finds no records when record is present.

SSRS Report chart labels overlapping