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

The Book of Redgate: Meetings

By

I think we might have forgotten this a bit, but on one of the...

New article: Automating SQL Server Builds

By

I refresh my test SQL Servers at least monthly with a fresh VM. Setting...

Leading with Accountability: How Extreme Ownership Transforms Leadership

By

Embracing Total Responsibility In every organization there comes a moment when teams must choose...

Read the latest Blogs

Forums

How to resolve issue of custom Audit log table containing incorrect data?

By Kevin8

We have created a parent table, child table & Audit log table in SQL...

Change Tracking Default Retention

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Change Tracking Default Retention

ssrs subscription file share

By jshumaker

I am trying to create a subscription that posts to a one drive directory. ...

Visit the forum

Question of the Day

Change Tracking Default Retention

I run this command on my SQL Server 2022 database:

ALTER DATABASE AdventureWorks2017 SET CHANGE_TRACKING = ON;
What is the default data retention period?

See possible answers