DataOnWheels

Steve Hughes is the Director of Consulting at 3Cloud. In my current role, I manage the West and Central Data & AI consultant team at 3Cloud. I did a similar role at Pragmatic Works before our merger with 3Cloud. I focus on team development and company growth with this role. In my previous role as a Principal Consultant Lead at Pragmatic Works, I focused on designing solutions for customers on Microsoft technologies including SQL Server, Power Platform, and Azure.

Kristyna Hughes is the Team Lead for BI at GlobalTranz. I have played an instrumental role in moving our company from 3 different reporting platforms to hosting our reporting within Power BI. I provide advice on security structures within the platform, manage the gateways, create and implement design strategies, train, and build reports for both our internal operations committee and external customers. I will also be aiding in embedding Power BI within an unified TMS and ensuring various levels of security are maintained within the embedded reports.

All authors

All authors

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