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

Measuring RAG Solutions: Are We Retrieving the Right Information?

By

A RAG pipeline that answers questions in the demo is not the same thing...

Advice I Like: Lots of Ideas

By

“A multitude of bad ideas is necessary for one good idea” – from Excellent...

Building a DBA Agent for Your SQL Server Estate with MCP

By

Yesterday I gave a talk for MSSQLTips called “Building a DBA Agent for Your...

Read the latest Blogs

Forums

How do I connect to a SQL Server database on my ISP?

By Doctor Who 2

I've got a web application for my side business. I've added a SQL Server...

Looking for New Blood

By Grant Fritchey

Comments posted to this topic are about the item Looking for New Blood

Server-Level Row Counts for Tables and Views

By Artur Sanin

Comments posted to this topic are about the item Server-Level Row Counts for Tables...

Visit the forum

Question of the Day

Hyperscale Replicas I

What types of secondary replicas are available for the Azure SQL Database Hyperscale edition?

See possible answers