Uncategorized

SQLServerCentral Editorial

The Impact of Small Changes

  • Editorial

A year ago, I started a monthly blogging event for the PostgreSQL community, inspired by T-SQL Tuesdays. I decided to call it PGSQL Phriday. (Time will tell if my insistence on trying to use a literation was a good idea or not.) Like the event for the SQL Server community, we ask someone to be […]

(1)

You rated this post out of 5. Change rating

2023-09-09

92 reads

SQLServerCentral Editorial

A Season of Reflection

  • Editorial

As I think about heading into the fall conference season (and seeing so many familiar faces!!), I realize that I'm going to be asking myself a set of familiar questions. Who am I? What skills do I need to improve on in the coming year? Who do I look up to in the community and […]

You rated this post out of 5. Change rating

2023-09-02

74 reads

SQLServerCentral Editorial

Be Prepared

  • Editorial

I've been reading about the fires in Maui and the horrible loss of life there. My heart goes out to all involved. I hope, if you can, you donate to a good charity to help those poor people. It also inspired me to do another check on our emergency supplies and equipment. No, we don't […]

(2)

You rated this post out of 5. Change rating

2023-08-26

101 reads

External Article

Managing Test Data for Database Development

  • Article

In coming up with a strategy for managing test data, first you need to understand what the many test requirements are likely to be for the particular database you are developing. Next, you need to create all the different categories of test data required to suite test requirements and, finally, work out how to manage it in a way that allows a test-driven approach to development.

Read more in this latest article from Phil Factor

2023-08-18

SQLServerCentral Editorial

Looking Back and Forward

  • Editorial

I took part in a podcast this week, Arrested DevOps. I did one with them once before, almost ten years ago. The host and I were both a little surprised that it had been so long. This caused us to look back a bit. Interestingly enough, ten years ago meant I was only about two […]

You rated this post out of 5. Change rating

2023-07-29

60 reads

Blogs

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

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