Press "Enter" to skip to content

Day: November 20, 2026

Group by Schema in SSMS

Jess Pomfret finds an option:

Folks, how have I missed this? I was at FabCon & SQLCon in Barcelona a few weeks ago, when I discovered (in a totally unrelated session!) that you can now group by schema in SQL Server Management Studio (SSMS). This little gem makes navigating certain databases so much easier. If you’ve ever worked in a database with hundreds of objects across many schemas, you’re going to love this.

Click through to see how.

Leave a Comment

Fuzzy String Matching now GA

Abhiman Tiwari promotes a feature:

MICROSFT isn’t MICROSOFT. MARHTA isn’t MARTHA. INV-1O08 isn’t INV-1008. To an equality check, each pair is simply different. To your business, each is a near miss worth catching.

Today, fuzzy string matching is generally available in Microsoft SQL. EDIT_DISTANCE tells you MICROSFT is one edit from MICROSOFT. JARO_WINKLER_SIMILARITY scores MARTHA and MARHTA at 96 out of 100. It all runs in T-SQL, right where your data lives, with no external libraries, models, or custom code.

As of CU11, this is now GA in SQL Server 2025.

Leave a Comment

IS DISTINCT FROM

Andy Brownsword tries out a shortcut:

Comparisons involving NULL-able values and columns are an early learning experience. I recently stumbled upon a relatively new way to handle these which I thought would be interesting T-SQL to share.

I think the two reasons you don’t see this in production are as follows. First, it requires a recent version of SQL Server, 2022 or later. A lot of the T-SQL code that went into training language models was for older versions of SQL Server. Second, because there’s no performance difference, people don’t spend a lot of time changing existing code to use this syntax. It’s a bit clearer in terms of intent, but otherwise doesn’t move the needle for people.

Leave a Comment

Finding NTLM Connections to SQL Server

Andreas Wolter shares advice and a script:

In short: I recommend finding out now which connections to your SQL Servers still use NTLM, and fixing them before Windows disables NTLM by default. Most of them fall back to NTLM silently, because of a missing SPN, a connection by IP address or an alias. SQL Server itself has no setting for this – the work is in Active Directory, DNS and client connection strings.

Click through for several reasons why users might be connecting via the old and deprecated protocol, and what to do about it.

Leave a Comment