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 […]
By ChrisJenkins
You could be tolerating limited reporting because there isn’t an off the shelf solution...
A while back I wrote a quick post on setting up key mappings in...
By Steve Jones
In 100 years a lot of what we take to be true now will...
Comments posted to this topic are about the item Lots of FKs
Comments posted to this topic are about the item Real-time On-prem SQL Server Data...
Comments posted to this topic are about the item Can You Let Go of...
In SQL Server 2025, what are the most outgoing and incoming FK references a table can have?
See possible answers