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