External Article

Defusing Database Time Bombs: Avoiding the Need to Refactor Databases

Where applications are evolved by gradually molding them to a growing understanding of the business domain, this presents great challenges to database development. If databases are designed too loosely, and initial errors are allowed to fester, the results become harder and harder to refactor until eventually they constitute a database time bomb. Thomas LeBlanc describes how to avoid a few basic, but very common, database time bombs.

Blogs

Narrow Task Decomposition in AI Pipeline Agents

By

A nightly load into sales_fact fails. Ask an orchestrating agent to break down the...

Car Update: August 2026

By

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

An architecture scenario Imagine separate Sales, Finance, Shared Data, and Executive Analytics workspaces. Sales...

Read the latest Blogs

Forums

Managing Incidents and Fighting Fires

By Pat Wright

Comments posted to this topic are about the item Managing Incidents and Fighting Fires

Backing Up a DMK

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Backing Up a DMK

The Quiet Part

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Quiet Part

Visit the forum

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