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 […]
I’ve been doing a deep dive into SQL Server on-disk structures lately, and one...
By DataOnWheels
Thanks to everyone who joined the blog party this month. I noticed three themes...
By Vinay Thakur
This week has training on AI – Cyber security experts – Omar Santos and...
Comments posted to this topic are about the item What's new in R 4.6
Comments posted to this topic are about the item Interesting Changes in R, which...
Comments posted to this topic are about the item PostgreSQL String Functions Part 1
When thinking about the identity property and sequence objects, which of these can generate values before an insert statement is executed?
See possible answers