2007-08-31
1,659 reads
2007-08-31
1,659 reads
I went and cleaned out the Central Publishing Group colocation cage at Viawest. We've been there for 3 years and...
2007-08-30
1,408 reads
2007-08-30
1,268 reads
2007-08-29
1,633 reads
It's an interesting debate on blogging in response to my editorial. I definitely thing blogging is worth a try. You...
2007-08-28
1,483 reads
2007-08-28
1,322 reads
2007-08-27
2,909 reads
Actually we had a long meeting with the developers this morning and PMs over a remote desktop session and I...
2007-08-24
1,387 reads
2007-08-24
1,532 reads
2007-08-23
1,150 reads
One feature that I have been waiting for years! The new announcement around optimize...
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
By DesertDBA
I haven’t posted in a while (well, not here at least since I’ve been...
hi, i noticed the sqlhealth extended event is on by default , and it...
Hi everyone, I’m looking for some guidance on a SQL Server performance issue I’ve...
Using New-AzSqlInstanceServerTrustCertificate to import a certificate and get the message New-AzSqlInstanceServerTrustCertificate: Long running operation...
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; goThen, 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