Jason Brimhall


Blog Post

Day 6 – Lost in Space

This is the sixth installment in the 12 day series for SQL tidbits during this holiday season. Previous articles in this mini-series on quick tidbits: SQL Sat LV announcement...

2013-12-30

2 reads

Blog Post

Day 5 – Peer Identity

This is the fifth installment in the 12 day series for SQL tidbits during this holiday season. Previous articles in this mini-series on quick tidbits: SQL Sat LV announcement...

2013-12-29

3 reads

Blog Post

Day 4 – Broken Broker

This is the fourth installment in the 12 day series for SQL tidbits during this holiday season. Previous articles in this mini-series on quick tidbits: SQL Sat LV announcement...

2013-12-28

19 reads

Blogs

Presenting with Visual Studio Code

By

A while back I wrote a quick post on setting up key mappings in...

Advice I Like: In 100 Years

By

In 100 years a lot of what we take to be true now will...

dataMinds Saturday 2026 – Slides

By

At Saturday the 21st of February I’m presenting an introduction to dimensional modelling at...

Read the latest Blogs

Forums

connections vs apis

By stan

hi , i hear more and more that we have too many connections to...

is it true we cant debug c# scripts in ssis anymore under vs

By stan

Hi, i'm running vs2022.   I'm trying out a c# script that i'd like to...

Missing the Jaro Winkler Distance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Missing the Jaro Winkler Distance

Visit the forum

Question of the Day

Missing the Jaro Winkler Distance

I upgraded a SQL Server 2019 instance to SQL Server 2025. I wanted to test the fuzzy string search functions. I run this code:

SELECT JARO_WINKLER_DISTANCE('tim', 'tom')
I get this error message:
Msg 195, Level 15, State 10, Line 1 'JARO_WINKLER_DISTANCE' is not a recognized built-in function name.
What is wrong?

See possible answers