Additional Articles


External Article

Handling Service Broker Errors

The previous installment of the 'SQL Server 2005 Express Edition' series discussed using transactions to protect the integrity and consistency of Service Broker-based communication. Depending on the type of issue encountered by our code, the outcome might be different from expected. This article demonstrates a more robust approach to error handling and applies it to our target.

2009-03-18

1,351 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

AllocationType as ROW_OVERFLOW_DATA

By inHouseDBA

Hello, I inherited a number of tables with like 20-30 column using nvarchar(256) in...

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

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