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

Why Database AI Agents need Layers?

By

Third part in my Ai series with databases. When building AI solutions within the...

Un-Migrating From the Cloud: T-SQL Tuesday #199

By

This month we have a very interesting invitation from Koen Verbeeck. He has hosted...

T-SQL Tuesday #199: Back to the on-prem

By

It’s the second tuesday of the month, which means T-SQL Tuesday time! This month’s...

Read the latest Blogs

Forums

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...

Secure Communications

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Secure Communications

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