External Article

Avoid External Dependencies in SQL Server Triggers

I sometimes want to perform auditing or other actions in a trigger based on some criteria. More specifically, there are a few cases that may warrant an e-mail; for example, if a web sale takes place that requires custom or overnight shipping and handling. It is tempting to just add code to the trigger that sends an e-mail when these criteria are met. But this can be problematic for two reasons: (1) your users are waiting for that processing to occur, and (2) if you can't send the e-mail, how do you decide whether or not to roll back the transaction, and how do you bring the problem to the attention of the administrator?

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