Database Weekly

SQLServerCentral Editorial

The Case for Patching

  • Editorial

Recently I was testing a feature in SQL Server on 2017 and 2019. There was supposed to be an improvement across versions, but I didn't see it. Then I realized that I was on SQL Server 2019 CU 2 on my laptop, and the current CU is 17. I took a few minutes to download […]

(2)

You rated this post out of 5. Change rating

2022-08-20

153 reads

SQLServerCentral Editorial

Moving on but not far

  • Editorial

During my technical career, I’ve changed companies several times. I even worked as an independent contractor for three years. One thing I have never done before was switch departments and roles within one company. That’s about to change in a couple of weeks as I move from Simple Talk Editor and DevOps Advocate in Marketing […]

(2)

You rated this post out of 5. Change rating

2022-05-21

103 reads

Blogs

RANK() vs DENSE_RANK(): #SQLNewBlogger

By

I haven’t done one of these in awhile, but I saw an article recently...

Using CAT for Testing of Data Agents

By

In last months one of the scenarios where you can use AI has been...

Read the latest Blogs

Forums

Missing the Jaro Winkler Distance

By Steve Jones - SSC Editor

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

25 Years Later: What SQLServerCentral Meant to Me

By Brian Knight

Comments posted to this topic are about the item 25 Years Later: What SQLServerCentral...

Doing Good at SQL Server Central

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Doing Good at SQL Server...

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