Prakash Heda

Prakash Heda works as Sr. Database Administrator at Advent Software. His expertise includes Performance Tuning/Troubleshooting, high availability, SAN configuration and windows administration. He has 13+ years of experience managing enterprise-wide data needs in both high volume transactional and data warehouse environments. Prakash holds certifications for MCDBA and MCITP. His background includes administration & development using VB/ASP/SSIS using SQL Server 2000, 2005 and 2008/R2 and SQL server 2012. He is an active member of PASS, SQL Saturday. He’s a frequent presenter at user groups, SQL Saturdays, and other community events. He is also an avid tweeter, blogger and runner.
  • Interests: Computers, Chess, Reading

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

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

Refactoring SQL Code

By Steve Jones - SSC Editor

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

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