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

610 reads

Blogs

Bicep Your Elastic Jobs

By

I posted on Terraform and Azure SQL last year but wanted to see what...

3rd Party Applications Have Issues

By

As a SQL DBA, what do you do when a vendor application has performance...

Check Azure SQL DB Space Used

By

A couple of days ago I was doing some cleaning on some Azure SQL...

Read the latest Blogs

Forums

The On-Call Load

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The On-Call Load

Two Table Hints

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Two Table Hints

Database Dashboards in Azure Data Studio

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Database Dashboards in Azure Data...

Visit the forum

Question of the Day

Two Table Hints

What happens when I run this code:

SELECT
  p.ProductName
, p.ProductCategory
FROM dbo.Product AS p WITH (NOLOCK, TABLOCK);

See possible answers