Editorials

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: )

626 reads

Blogs

Git forked

By

Forgive me for the title. Mentally I’m 12. When I started my current day...

Setting FK Constraints in Data Modeler

By

One of the things a customer asked recently about Redgate Data Modeler was how...

Webinar: Navigating the Database Landscape in 2026

By

For a number of years, we’ve produced the State of the Database Landscape report,...

Read the latest Blogs

Forums

Expanding into Print

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Expanding into Print

Downtime Caused by the Postgres Transaction ID Wraparound Problem

By Chandan Shukla

Comments posted to this topic are about the item Downtime Caused by the Postgres...

The String Distance I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The String Distance I

Visit the forum

Question of the Day

The String Distance I

In SQL Server 2025, what is returned by this code:

SELECT EDIT_DISTANCE('Steve', 'Stan')
Assume preview features are enabled.

See possible answers