TABLOCK Hint can Negatively Impact SQL Server Concurrency
In this article, we look at how using the Tablock hint in SQL Server could impact concurrency and block other sessions.
2023-11-29
Concurrency
Concurrency Challenges Around Schema Changes
A post on distributed systems and how schema changes are handled caught Steve's eye. See if you agree with how he thinks this should work.
2023-06-26
140 reads
Lock Scenarios Using sys.dm_tran_locks
Learn about the impact of locking and blocking in sessions through some demonstrations of different types of actions.
2020-06-11
7,990 reads
Concurrency Control in SQL Server
Learn a bit about concurrency problems in SQL Server, the issues they create, and the different isolation levels that help you solve them.
2020-05-12
42,139 reads
Prevent SQL Server Blocking using Lock_Timeout
In this tip we look at a way to minimize the length of blocking using SQL Server lock timeout.
2020-01-24
The Many Levels Of Concurrency
When designing for high concurrency, most people look to the hardware for answers. And while it’s true that it plays an important role, there’s a heck of a lot more to it.
2018-03-06
3,361 reads
2013-08-06
2,011 reads
Free eBook: Understanding SQL Server Concurrency
When you can’t get to your data because another application has it locked, a thorough knowledge of SQL Server concurrency will give you the confidence to decide what to do.
2020-11-11 (first published: 2013-07-17)
106,148 reads
Blogs
Advice I Like: Art
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
Why Optimize CPU for RDS SQL Server is a game changer
One feature that I have been waiting for years! The new announcement around optimize...
Performance tuning KubeVirt for SQL Server
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
Forums
The AI Bubble and the Weak Foundation Beam
Comments posted to this topic are about the item The AI Bubble and the...
data type gets lost in data flow
Hi, in a simple oledb source->derived column->oledb destination data flow, 2 of my...
i noticed the sqlhealth extende event is on by default , so can i reduce
hi, i noticed the sqlhealth extended event is on by default , and it...
Question of the Day
The Read Committed Snapshot Isolation behaviour
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers