Andy Warren

I started my SQL journey here at SQLServerCentral as one of the founders, helping to build a place to share and learn that continues to thrive under the editorial guidance of my friend Steve Jones. I've done a lot of volunteer work over the years ranging from our local SQL group (oPASS, SQLOrlando) to serving on the Board of Directors of PASS to designing and building the framework of SQLSaturday (which has gone on to produce more than 1000 locally managed events since we started in 2007). These days I manage a DBA team, but over the years I've been a trainer, consultant, contractor, and DBA. I'm rarely present on social media, the best way to contact me is here, LinkedIn, or via email.

All authors

All authors

Blogs

Advice I Like: Art

By

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

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,...

Read the latest Blogs

Forums

data type gets lost in data flow

By stan

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

By rajemessage 14195

hi, i noticed the sqlhealth extended event is on by default , and it...

New-AzSqlInstanceServerTrustCertificate - Failed and no clues

By BrainDonor

Using New-AzSqlInstanceServerTrustCertificate to import a certificate and get the message New-AzSqlInstanceServerTrustCertificate: Long running operation...

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