The End of SQL Server 2019
Steve has a few thoughts after the end of mainstream support for SQL Server 2019.
2025-03-26
787 reads
Steve has a few thoughts after the end of mainstream support for SQL Server 2019.
2025-03-26
787 reads
Batch execution mode is a new optimization feature in SQL Server. In this Article, we'll explore how Batch execution mode works and how you can use it to get faster query results on Rowstore data.
2023-10-30
4,434 reads
This week Steve found a question of whether SQL Server 2019 uses more CPU than 2016.
2023-04-01
711 reads
2023-03-13
406 reads
2021-09-08
821 reads
In this article we look at the Hybrid Buffer Pool available in SQL Server 2019 and how to enable and disable this feature for SQL Server.
2021-08-09
2021-04-27
838 reads
2021-02-25
521 reads
2021-02-11
783 reads
I have explored the SQL Server 2019, Intelligent Query Processing Feature – “Table Variable Deferred Compilation”.
The script contains some theory at the top and links to read.
After that, there are required queries to run on SQL Server 2019.
This way we can see the feature in action and look at it's strengths and caveats.
2020-08-03
1,627 reads
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
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,...
Hi, in a simple oledb source->derived column->oledb destination data flow, 2 of my...
hi, i noticed the sqlhealth extended event is on by default , and it...
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