Articles

SQLServerCentral Article

Auditing Your SQL Server Environment Part I

Ever been placed into a new environment and couldn't
find an ounce of documentation? This article is the first in a series that will help you make an audit of your new environment
and determine if any SQL Server login does not have a password, has a password the same as the login name or a password that is only one character long.

(1)

You rated this post out of 5. Change rating

2002-04-02

10,441 reads

SQLServerCentral Article

Non-Continous Replicaton and The LogReader

Last year Andy wrote about turning off the log reader as a way to reduce the overhead on a server, primarily when you have many logreaders running. In this follow up article he talks about the downside of using this technique and how the behavior of the logreader can be "tweaked" to make using non-continuous replication a little less of a headache.

(1)

You rated this post out of 5. Change rating

2002-03-28

5,155 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...

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