Editorial

SQLServerCentral Editorial

Updating Aging Databases

  • Editorial

Somehow, one is expected to be pleased that SQL Server 2005 is going to have another Service Pack. Why? For many DBAs, SQL Server 2005 is still a dangerous and radical upgrade. Phil Factor considers Microsoft's responsibilities...

2008-10-28

197 reads

SQLServerCentral Editorial

Barriers to Entry, Database Weekly (Oct 27 2008)

  • Editorial

Many people who spend time contributing to technical forums bemoan the increasing amount of time and energy they expend trying to help people who seem unwilling or unable to help themselves. At the same time, they say, the courtesy is deteriorating and the number of people willing to "stir things up" for the sake of it increases. Is there a solution to this?

You rated this post out of 5. Change rating

2008-10-27

109 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...

RANK() vs DENSE_RANK(): #SQLNewBlogger

By

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

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