2015-05-13
1 reads
2015-05-13
1 reads
2015-05-13
1 reads
This session is mostly demo-focused. I will cover prerequisites for scripts and show how to do multiple SQL Server installations...
2015-05-02
635 reads
2015-05-02
3 reads
2015-05-02
6 reads
2015-05-02
7 reads
This session is mostly demo-focused. I will cover prerequisites for scripts and show how to do multiple SQL Server installations using scripts and demonstrate how to Streamline SQL Server...
2015-05-02
3 reads
2015-03-03
1 reads
2015-03-03
2015-03-03
2 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