Time Bomb Design - A Longer Fuse
In a sequel to his first article on Time Bomb Design, David Poole examines the issues we find between development environments and production ones.
SQL Server MasterClass with Kimberly Tripp and Paul Randal
If you will be in London on June 17th, this is an event you do not want to miss.
Working with Spatial Data Part IV - Developing a Geospatial Dashboard (GIS)
In Part IV of the Geo-Spatial series, an interactive dashboard is developed to present and interact with the data.
Query-generated Column Expressions
A technique from Bill Nicolich that allows you to target columns by data type for the same custom expression and easily build complex queries.
The Death March
Are you working too hard? Is it worth it? Steve Jones says that it is not and that you should push back.
Showplan Operator of the Week – BookMark/Key Lookup
Fabiano continues in his mission to describe the major Showplan Operators used by SQL Server's Query Optimiser. This week he meets a star, the Key Lookup, a stalwart performer, but most famous for its role in ill-performing queries where an index does not 'cover' the data required to execute the query. If you understand why, and in what circumstances, key lookups are slow, it helps greatly with optimising query performance.
A Smarter Planet
IBM has this tagline about a smarter planet and has a great video about the Internet of Things. Steve Jones looks at some of the issues we might have in actually using all this data.
Clustered Indexes? Sedimentary, my dear Watson
There is much sound advice suggesting that every table should have a clustered index, and that narrow, integer, ever-increasing columns, such as afforded by an IDENTITY column are the best choice. But is the sedimentary approach really the natural order of the day?
Optimising Server-Side Paging - Part II
The second part of this series compares four methods of obtaining the total number of rows in a paged data set.
Analyzing I/O Characteristics and Sizing Storage Systems for SQL Server Database Applications
Understanding how to analyze the characteristics of I/O patterns in the Microsoft® SQL Server® data management software and how they relate to a physical storage configuration is useful in determining deployment requirements for any given workload. A well-performing I/O subsystem is a critical component of any SQL Server application. I/O subsystems should be sized in the same manner as other hardware components such as memory and CPU. As workloads increase it is common to increase the number of CPUs and increase the amount of memory. Increasing disk resources is often necessary to achieve the right performance, even if there is already enough capacity to hold the data.
Blogs
Narrow Task Decomposition in AI Pipeline Agents
A nightly load into sales_fact fails. Ask an orchestrating agent to break down the...
Car Update: August 2026
By Steve Jones
It’s been some time since I provided a car update, so I decided to...
Microsoft Fabric OneLake Shortcuts: When to Use Them and When Not To
By James Serra
An architecture scenario Imagine separate Sales, Finance, Shared Data, and Executive Analytics workspaces. Sales...
Forums
Backing Up a DMK
Comments posted to this topic are about the item Backing Up a DMK
The Quiet Part
Comments posted to this topic are about the item The Quiet Part
BIT_COUNT in SQL Server
Comments posted to this topic are about the item BIT_COUNT in SQL Server
Question of the Day
Backing Up a DMK
In SQL Server 2025, I have a database with a Database Masker Key (DMK). I want to back up this key and keep a copy offline. When do I have to open this key before running the backup?
See possible answers