Tony Davis

  • Interests: football, modern literature, real ale

SQLServerCentral Editorial

Are Triggers a "Legacy" Feature?

It is late evening. Something is wrong with a database. You narrow down the possibilities, getting more frustrated and puzzled. Stay calm. Check the inputs systematically. No! The data going into that table is right, but when you then read it in the table, it's wrong. Why did I stop believing in the supernatural? Then it hits you. Every time it comes as a surprise. They're using triggers. (This editorial was originally published on Nov 10, 2008)

You rated this post out of 5. Change rating

2013-02-19 (first published: )

624 reads

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