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

Database AI Agents: The Read-Only Rule

By

Fourth in a series on Ai and databases. What Read-Only Advisory Actually Means A...

Creating a SQL Stored Procedure to Load a SCD2

By

This is a blog that I am writing for future me and hopefully it’ll...

Funny Money: #SQLNewBlogger

By

While wandering around the documentation looking for some Question of the Day topics, I...

Read the latest Blogs

Forums

Backup Availability Group

By jayoub

Please I am hoping for some feedback Specifications: Windows Server 2022 SQL Server 2022...

How Do the Experts Become Experts?

By Kathi Kellenberger

Comments posted to this topic are about the item How Do the Experts Become...

Stairway to Reliable Database Deployments Level 4 – Preparing for Production Deployment

By Massimo Preitano

Comments posted to this topic are about the item Stairway to Reliable Database Deployments...

Visit the forum

Question of the Day

Secure Communications

As of June 2026, what is the best version of TLS to use with SQL Server?

See possible answers