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

I recommend Smart Brevity (book) for communications

By

Following the advice in Smart Brevity improves communication.

SQL Server 2025 Developer Edition – One size fits all

By

Microsoft has released SQL Server 2025, bringing big improvements to its main database engine....

Monday Monitor Tips: Learning While Using the Tool

By

A customer was asking about what certain items in Redgate Monitor mean. They have...

Read the latest Blogs

Forums

Switch partition: NULL boundary id

By vpolasa

I have table: t1 in schema1 with 19 billion records. I have another table...

Minimally Viable Security

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Minimally Viable Security

Encoding NULL

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Encoding NULL

Visit the forum

Question of the Day

Encoding NULL

What is returned from this code in SQL Server 2025?

SELECT BASE64_ENCODE(NULL)

See possible answers