The End of SQL Server 2019
Steve has a few thoughts after the end of mainstream support for SQL Server 2019.
2025-03-26
311 reads
Steve has a few thoughts after the end of mainstream support for SQL Server 2019.
2025-03-26
311 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
3,953 reads
This week Steve found a question of whether SQL Server 2019 uses more CPU than 2016.
2023-04-01
680 reads
2023-03-13
401 reads
2021-09-08
811 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
834 reads
2021-02-25
515 reads
2021-02-11
781 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,591 reads
It’s been forgotten about and neglected for few years but I’ve decided to dust...
I am honored to announce that I have been renewed as a Microsoft MVP...
By Rohit Garg
🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item Navigating Multi Platform Realities in...
I have tried a number of times to export and then import my SSMS...
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers