Evergreen SQL Server
Microsoft talks about evergreen SQL, where you never need to patch your database.
2025-05-14 (first published: 2019-07-24)
1,591 reads
Microsoft talks about evergreen SQL, where you never need to patch your database.
2025-05-14 (first published: 2019-07-24)
1,591 reads
2025-05-14
603 reads
It’s that time of the month again, when the T-SQL Tuesday blog party takes place. I manage this site, and am looking for hosts all the time. This month...
2025-05-13
25 reads
2025-05-12
275 reads
lookaback– n. the chock of meeting back up with someone and learning that your mental image of them had fallen wildly out of date – having grown up or...
2025-05-09
19 reads
DevOps and databases aren't always considered compatible, but that is changing. DORA now has recommendations for database changes on their site.
2025-05-09
163 reads
2025-05-09
509 reads
Steve looks at a trial using Microsoft's Copilot and how helpful it was for workers.
2025-05-07
175 reads
In a couple of weeks, I’ll be in New York City for the Redgate DevOps Devour Hour Lunch and Learn. This is at the Industrious office at 730 3rd...
2025-05-07
20 reads
2025-05-07
440 reads
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
By Brian Kelley
On Patch Tuesday, in addition to OS and Office security patches, Microsoft also released...
When mirroring was first released for Azure SQL Database, it used Change Data Capture...
Comments posted to this topic are about the item Multiple Deployment Processes
Comments posted to this topic are about the item How to Use sqlpackage to...
Comments posted to this topic are about the item Upgrading Admin Queries
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