Articles

Technical Article

Transaction locking and row versioning guide

In any database, mismanagement of transactions often leads to contention and performance problems in systems that have many users. As the number of users that access the data increases, it becomes important to have applications that use transactions efficiently. This guide describes the locking and row versioning mechanisms the SQL Server Database Engine uses to ensure the physical integrity of each transaction and provides information on how applications can control transactions efficiently.

You rated this post out of 5. Change rating

2022-10-05

External Article

Redgate Summit: The Database DevOps Transformation

Digital transformation and data modernization are frequently cited as high-value strategic projects that are crucial to achieving competitive advantage. At the same time, delivery of code in agile and predictable ways has led to many businesses adopting DevOps practices. Throughout this event we will explore how Database DevOps can be the function that accelerates transformation projects.

Join us On October 6th as we invite experts to share their insider tips and tricks.

2022-09-28

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