Source Code Security
The code you use may contain security information. Be extra careful in this case, especially when you use encryption.
Getting Started with Database Engine Tuning Advisor in SQL Server – Part 2
Arshad Ali demonstrates how you can use the command line interface to tune SQL queries and how you can use SQL Server Profiler to capture the workload for tuning with Database Engine Tuning Advisor.
SQL Monitor Custom Metric: Hash Warnings (Last Hour)
This alert is raised when the number of hash warnings events in the last hour goes above a specified threshold. A hash warning event means that part of the data processed for a hash operation was written to tempdb during query execution, which can degrade SQL Server Performance.
Obedience Training For Databases: Cascading Constraints
In which Phil Factor illustrates in TSQL how it is possible to use foreign key constraints to enforce data rules, and illustrates some surprising consequences of using cascading.
One Rule, Umpteen Constraints
Despite being deprecated for many years, Phil Factor explains why RULEs are still hanging on in there in SQL Server 2014.
Identifying and Solving Index Scan Problems
When you're developing database applications, it pays to check for index scans in the SQL Server query plan cache. Once you've identified the queries, what next? Dennes Torres gives some preliminary guidelines on how to find out why these index scans are being chosen for these queries and how to make the queries run faster and more efficiently.
Cumulative sum of previous rows
I had an update statement that took 3 minutes to run after this code change it took 6 seconds.
Azure Blob Storage Part 9: Shared Access Signatures
In this article, Robin Shahan talks about security and how to control access to containers and blobs using shared access signatures (SAS) and stored access policies.
Efficiency
This Friday Steve Jones asks about how you are tackling your career growth as you get older. Are you getting more efficient?
Self-maintaining, Contiguous Effective Dates in Temporal Tables
'Temporal' tables contain facts that are valid for a period of time. When they are used for financial information they have to be very well constrained to prevent errors getting in and causing incorrect reporting. This makes them more difficult to maintain. Is it possible to have both the stringent constraints and simple CRUD operations? Well, yes. Dwain Camps patiently explains the whole process.
Blogs
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Shifting Mindsets: Why FinOps is Essential for Cloud Efficiency
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
Forums
Windows logins for users migrated from DomainA to DomainB
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Multiple Deployment Processes
Comments posted to this topic are about the item Multiple Deployment Processes
How to Use sqlpackage to Detect Schema Drift Between Azure SQL Databases
Comments posted to this topic are about the item How to Use sqlpackage to...
Question of the Day
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