January 16, 2026 at 12:00 am
Comments posted to this topic are about the item T-SQL in SQL Server 2025: Fuzzy String Search I
January 16, 2026 at 3:59 pm
It's nice to have such a tool in the toolbox (just in case), but I find it hard to find a real use case.
Maybe to compare public names as for countries, states, cities or even streets, but for surenames in your example it is hard (at least when you want to automate it / use it to correct spellings in a larger data set) - your second last exampled showes "Estaban" as very close to "Stephen".
God is real, unless declared integer.
January 16, 2026 at 5:16 pm
Agreed. I do think it could be useful as a "picklist" for misspellings or typos more than trying to determine Estaban is Stephen or Steve and Stephen are the same.
I see this more as a way to reduce the things someone has to look at for data quality.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply