2026-02-04
1,127 reads
2026-02-04
1,127 reads
2026-02-04 (first published: 2026-02-03)
107 reads
2026-02-02
316 reads
2026-01-28
424 reads
2026-01-26
390 reads
In the last article, we examined fuzzy string matching in SQL Server 2025 with a few new functions. We know comparing strings has always been hard when we don't have great data quality. If we need exact matches, SQL Server works great. However, we often expect users to enter values without typos and know what […]
2026-01-23
2,046 reads
2026-01-21
461 reads
sp_helptext has served SQL Server DBAs for years, but it has its very obvious – and many – limitations: broken lines, missing triggers, no help with encrypted objects, to name just a few. That’s where sp_showcode comes in…
2026-01-21
After years of writing T-SQL a certain way, changing can be tough. When comparing tables for missing rows, developers often use LEFT JOIN.
2026-01-19
2026-01-19
512 reads
By ChrisJenkins
Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers