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
The challenges of managing lots of system are significant and there aren't easy solutions, but Steve has a few thoughts on what you can do.
2024-11-18
236 reads
2024-05-29
290 reads
Recently I was testing a feature in SQL Server on 2017 and 2019. There was supposed to be an improvement across versions, but I didn't see it. Then I realized that I was on SQL Server 2019 CU 2 on my laptop, and the current CU is 17. I took a few minutes to download […]
2022-08-20
149 reads
A new vulnerability for SQL Server is covered by a number of patches this week.
2022-06-18
733 reads
We will see databases deployed on the edge, and we will need strong security patches.
2021-12-20
290 reads
SQL Server 2016 SP3, the last service pack ever is out. Steve comments on how the world of software patches has changed.
2021-10-08
532 reads
Having a patching strategy for your systems is important, and Steve notes that you ought to be organized and allow for some flexibility when designing one.
2021-06-30
337 reads
2021-04-10
122 reads
This script can install Service pack, security patch and Cumulative update on SQL instance(Database Engine).
2020-05-26 (first published: 2020-05-19)
1,761 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