Articles

SQLServerCentral Article

Worst Practice - Bad Connection Strings and Bad Info in Sysprocesses

Andy returns to the Worst Practice series this week with a short article looking at how connection strings in applications affect what you see in sysprocesses. Perhaps less controversial (in our opinion) that some of the other worst practices, this is something easy to fix and definitely worth fixing! Read the article and post a comment - explore other points of view! Readers posting a comment will be entered in a drawing for a copy of the SQL Server 2000 Resource Kit.

You rated this post out of 5. Change rating

2003-08-01

15,787 reads

Technical Article

SQLCentric

This is an update to v1.2 of the product which does monitoring of your SQL servers. Looks like it checks service status, jobs, disk space, some other things. (Not Reviewed)

2003-08-01

1,425 reads

Technical Article

MZTools - Addin for VB6

Freeware! This add-in gives you some great extra features when working in VB6. It has a tab index setter, options to add a chunk of error handling code, a simple code analyzer that gives you some metrics, and my favorite - an option to identify unused code and variables. If you're still using VB6 it's worth trying.

2003-07-30

1,541 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...

dataMinds Saturday 2026 – Slides

By

At Saturday the 21st of February I’m presenting an introduction to dimensional modelling at...

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