2026-03-06
588 reads
2026-03-06
588 reads
2026-03-04 (first published: 2026-02-27)
794 reads
2026-02-13
979 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,223 reads
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 values they want to find. Or at least know part of the string. However, matching with wildcards or partial strings […]
2026-01-28 (first published: 2026-01-16)
3,325 reads
Learn about the new string similarity functions in Azure SQL Database.
2025-03-28
8,847 reads
An optimized Damerau-Levenshtein Distance (DLD) algorithm for "fuzzy" string matching in Transact-SQL 2000-2008
2014-01-10 (first published: 2012-09-18)
31,338 reads
Roll Your Own Fuzzy Match / Grouping (Jaro Winkler) - T-SQL
2009-06-10
45,570 reads
Recently, in an attempt to thwart leechers (1990s kids will know), I added some...
Once upon a time I had a series about some cool stuff in Snowflake:...
By Steve Jones
“Most overnight successes – in fact any significant successes – take at least 5...
Comments posted to this topic are about the item Why Successful SQL Server Backups...
Comments posted to this topic are about the item Adding Bits II
Comments posted to this topic are about the item An Unlimited Token Budget
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, true)
GO
See possible answers