The End of SQL Server 2019
Steve has a few thoughts after the end of mainstream support for SQL Server 2019.
2025-03-26
1,206 reads
Steve has a few thoughts after the end of mainstream support for SQL Server 2019.
2025-03-26
1,206 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
257 reads
2024-05-29
295 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
153 reads
A new vulnerability for SQL Server is covered by a number of patches this week.
2022-06-18
747 reads
We will see databases deployed on the edge, and we will need strong security patches.
2021-12-20
300 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
546 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
346 reads
2021-04-10
123 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,817 reads
By Brian Kelley
My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...
By Steve Jones
“On the way to a grand goal, celebrate the smallest victories as if each...
Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...
Ruko Taman Kedoya Permai, Blok A 1A, No No.4-5, RT.11/RW.5, Kb. Jeruk, Kec. Kb....
Jl. Jenderal Sudirman No.21, RT.10/RW.1, Kuningan, Karet Kuningan, Kecamatan Setiabudi, Kota Jakarta Selatan, Daerah...
Jl. Kh Ahmad Dahlan No.25, Karangkidul, Kec. Semarang Tengah, Kota Semarang, Jawa Tengah 50136
How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?
See possible answers