The End of SQL Server 2019
Steve has a few thoughts after the end of mainstream support for SQL Server 2019.
2025-03-26
328 reads
Steve has a few thoughts after the end of mainstream support for SQL Server 2019.
2025-03-26
328 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
734 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
338 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
By Daniel Janik
Boost Your Azure Fabric Pipelines: Don’t Overlook This Crucial Spark Setting Are your Azure...
By Kevin3NF
The SQL Server installer has gotten better: tempdb configuration, MAXDOP, and even max memory...
By Rohit Garg
In the fast-paced world of IT, Database Administrators (DBAs) are the unsung heroes who ensure that...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item Monitor SQL Server using Zabbix
Hi We have databases with data stored for over 20 years, this is required...
You're troubleshooting a connectivity issue between a client application and a remote SQL Server instance. The client receives a "provider: TCP Provider, error: 0 - No such host is known" message. You verify that SQL Server is running and reachable on the server. The SQL Server instance is configured with a named instance and uses dynamic ports. Which of the following steps is most likely to resolve the issue?
See possible answers