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

617 reads

Blogs

Prepping for Certification, Part 1 of ?

By

I thought it would be good to put my thoughts down on how to...

How to Avoid Knowledge Stagnation

By

You want the short answer? Well, the only antidote to knowledge stagnation is probably...

Demystifying Fabric Workspaces: The Nerve Center of Your Data Universe

By

It always starts the same way. You open your laptop on a Monday morning,...

Read the latest Blogs

Forums

Guidelines and Requirements

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Guidelines and Requirements

Copying Production Schema

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Copying Production Schema

Workspace Identity Authentication for your Power BI Semantic Models in Microsoft Fabric

By Koen Verbeeck

Comments posted to this topic are about the item Workspace Identity Authentication for your...

Visit the forum

Question of the Day

Copying Production Schema

If I use DBCC CLONEDATABASE, can I remove some of the information from the copy?

See possible answers