Editorials

SQLServerCentral Editorial

Knowing When to Respond

I ran into this quote on the Microsoft Learn site, which I thought was a great way to think about how to administer a system: "Without a baseline, every issue encountered could be considered normal and therefore not require any additional intervention." When I've had users file tickets or complain about things not working well, […]

You rated this post out of 5. Change rating

2022-01-24

135 reads

SQLServerCentral Editorial

It Isn't Worth Automating

Every year I'm responsible for a portion of the Database Weekly newsletters. I used to do half, but right now Kathi, Grant, and I are on a rotation. Our boss puts out a schedule each year, which tells me the weeks for which I am responsible. Each January I then set up a recurring appointment […]

You rated this post out of 5. Change rating

2022-01-17

186 reads

SQLServerCentral Editorial

T-SQL Requires the Right Approach

Some of the most problematic T-SQL code I’ve seen over the years originated because the developer approached T-SQL with techniques more suitable for developing applications. I often saw these issues in my consulting days and always took the opportunity to teach the customer instead of only fixing the problems. One reason is that SQL is […]

(2)

You rated this post out of 5. Change rating

2022-01-15

216 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