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,765 reads
Steve has a few thoughts after the end of mainstream support for SQL Server 2019.
2025-03-26
1,765 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
310 reads
2024-05-29
336 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
203 reads
A new vulnerability for SQL Server is covered by a number of patches this week.
2022-06-18
779 reads
We will see databases deployed on the edge, and we will need strong security patches.
2021-12-20
341 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
589 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
383 reads
2021-04-10
159 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,889 reads
By Steve Jones
I had seen these roles in various instances, but never dug into the new...
By Brian Kelley
During COVID, I attended training on software/enterprise architecture given by Mark Richards. One of...
For me, the objective is straightforward: have a backup strategy that is reliable, understandable,...
Has anyone encountered recurring request latency when using Microsoft Access with SQL Server 2025...
Comments posted to this topic are about the item The ##MS_DatabaseConnector## User
Comments posted to this topic are about the item Planning for Change
On SQL Server 2025, I run this code as a sysadmin:
CREATE LOGIN Demo WITH PASSWORD = 'Demo1234567' GO ALTER SERVER ROLE ##MS_DatabaseConnector## ADD MEMBER Demo GOI then login as Demo and run this:
USE sandbox go SELECT CURRENT_USERWhat is returned? See possible answers