StraightforwardSQL

Blog Post

My Toolbox - Everything

Foreword
Not everything in the general sense, but a tool called Everything by voidtools (Download link). Usually, I have to make this distinction when googling.
No matter how great is my...

2022-09-27

37 reads

Blog Post

My Toolbox - Greenshot

Foreword
A picture is worth a thousand words. I use screenshots daily, whether it’s to share results, how-to tutorials, point out mistakes or create memes.
None of the tools I’ve tried...

2022-08-11

45 reads

Blog Post

What's in a name? (T-SQL Tuesday #152)

Foreword
This month’s invitation is from Deborah Melkin (b|t), about venting anything you want. So let’s start this rant.

There are only two hard things in Computer Science: cache invalidation and...

2022-07-29 (first published: )

279 reads

Blogs

Why Optimize CPU for RDS SQL Server is a game changer

By

One feature that I have been waiting for years! The new announcement around optimize...

Performance tuning KubeVirt for SQL Server

By

Following on from my last post about Getting Started With KubeVirt & SQL Server,...

T-SQL Tuesday #193 – A Note to Your Past, and a Warning from Your Future

By

I haven’t posted in a while (well, not here at least since I’ve been...

Read the latest Blogs

Forums

Refactoring SQL Code

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Refactoring SQL Code, which is...

The Read Committed Snapshot Isolation behaviour

By Alessandro Mortola

Comments posted to this topic are about the item The Read Committed Snapshot Isolation...

Working with JSON/JSONB Data in PostgreSQL using Python

By sabyda

Comments posted to this topic are about the item Working with JSON/JSONB Data in...

Visit the forum

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;
go
Then, 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