External Article

Developing Modifications that Survive Concurrency

You can create a database under the assumption that SQL looks after all the problems of concurrency. It will probably work fine under test conditions: then, in the production environment, it starts losing data in subtle ways that defy repetition. It is every Database Developer's nightmare. In an excerpt from his acclaimed book, Alex Kuznetsov explains why it happens, and how you can avoid such problems.

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