Part 1: How to solve the transactional issues of isolation levels
Transaction Isolation levels are described in terms of which concurrency side-effects, such as dirty reads or phantom reads, are allowed.
2013-05-01
10,118 reads
Isolation Levels
2012-11-21
2,105 reads
2012-04-19
2,012 reads
2010-07-06
3,085 reads
2009-03-19
3,975 reads
2009-03-05
3,682 reads
Using NOLOCK and READPAST table hints in SQL Server
Table locking hints provide developers much tighter control of their transactions. Look at the benefits and disadvantages of using the NOLOCK and READPAST table hints in SQL Server
2008-07-15
5,492 reads
Blogs
RANK() vs DENSE_RANK(): #SQLNewBlogger
By Steve Jones
I haven’t done one of these in awhile, but I saw an article recently...
Using CAT for Testing of Data Agents
In last months one of the scenarios where you can use AI has been...
Forums
Missing the Jaro Winkler Distance
Comments posted to this topic are about the item Missing the Jaro Winkler Distance
25 Years Later: What SQLServerCentral Meant to Me
Comments posted to this topic are about the item 25 Years Later: What SQLServerCentral...
Doing Good at SQL Server Central
Comments posted to this topic are about the item Doing Good at SQL Server...
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