This article discusses sp_PerfSQ a diagnostic tool designed to quantify performance features of database queries with active requests. It includes a behavioural parser and can assist in troubleshooting complex performance issues.
2021-12-24 (first published: 2019-12-02)
11,501 reads
2020-03-03 (first published: 2019-11-25)
10,687 reads
A forum question came up a few days ago regarding an abnormally large procedural cache. In an attempt to help out, I threw together a few ideas (some wrong, some right) and started looking at the types of query that were in the cache. A lot of the queries were in the format select * […]
2019-11-11
4,800 reads
2019-10-28
7,209 reads
2019-06-10
1,100 reads
2019-05-24
Batch Cussidy In the last post, we looked at how S...
2019-05-24
Watch this week’s episode on YouTube. SQL Server...
2019-05-22
2019-05-22
Footnote I have two queries. They return the same number of rows. The only difference is one column in the…
2019-05-20
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...
Comments posted to this topic are about the item Refactoring SQL Code, which is...
Comments posted to this topic are about the item The Read Committed Snapshot Isolation...
Comments posted to this topic are about the item Working with JSON/JSONB Data in...
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