When there’s a performance emergency, a lot of us perform the same manual tasks over and over. We run sp_BlitzWho or sp_WhoIsActive, look for blocking, long-running or out-of-control queries, and kill them.
See how Claude Code helped load a lot of messy data into a database for less than $5.
Today Steve talks about the need for a basic level of security in our software.
Sometimes we cannot improve query performance because we don’t have control over the code. Consider a query that is generated by Entity Framework (EF) from the application and you do not have access to the source code. The main question is how you can improve SQL Server query optimization for a poorly performing query?
In this article, I will provide a set of examples to show case the use of OUTPUT clause for INSERT and DELETE statements.
This article covers the 10 key concepts developers should understand to avoid surprises and to use the model database intentionally.
In this article, I am going to explain fixing a problem related login failure error with SQL Server. The Problem One of the common error in the SQL Server error log is "Login failed for user 'DomainName\ServerName$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]". Even though it says that […]
In last months one of the scenarios where you can use AI has been...
By ChrisJenkins
Do you spend so long manipulating your data into something vaguely useful that you...
By Steve Jones
It was neat to stumble on this in the book, a piece by me,...
I have two challenges XML source control not displaying the XML file parent node...
Thanks in advance for any clues on this. I am trying to write a...
Comments posted to this topic are about the item Backup to Immutable Storage
In SQL Server 2025, a backup can be made on Azure Immutable Storage. What changes in how the backup is created?
See possible answers