The Bleeding Edge Versus N Minus One
Risk-averse managers are reticent to upgrade to the latest and greatest. Why is this the case and how can the savvy DBA make the case for and get ready for a newer version of SQL Server?
2016-06-28
2,891 reads
Risk-averse managers are reticent to upgrade to the latest and greatest. Why is this the case and how can the savvy DBA make the case for and get ready for a newer version of SQL Server?
2016-06-28
2,891 reads
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
Hi everyone I asked this earlier but the desired outcome is a bit different...
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Comments posted to this topic are about the item Multiple Deployment Processes
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers