THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Merrill Aldrich

Trigger Authoring Decision Tree

TriggersDecisionTree

Published Wednesday, March 06, 2013 11:46 AM by merrillaldrich

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

AlexK said:

Well this is a nice diagram, but we do not have any triggers in our system, so I will not have a chance to use it ;).

March 6, 2013 2:06 PM
 

@kevine323 said:

I sent this to the devs as soon as I saw it. Thanks!

March 6, 2013 3:13 PM
 

merrillaldrich said:

Alex - there's a term for that. Let me think ... oh yeah, "success."

March 6, 2013 3:49 PM
 

Greg Milner said:

Thanks for lightening my day. I was just dealing with a stupid trigger on a client machine yesterday.

March 6, 2013 3:53 PM
 

Piotr said:

Merril - I don't quite understand the "Selet all > Delete" box. Could you please enlighten me?

March 7, 2013 2:38 AM
 

SqlChow said:

This just made my day.

March 7, 2013 10:45 AM
 

Peter Schott said:

Actually the other part of this is "do you have any devs who can take the time to do this right now?" :P Several times we've had to put something like this in a trigger because getting a dev to actually dig through the code to implement would take significantly longer before it ever got implemented.

March 7, 2013 11:16 AM
 

Nic said:

Love it! How many times have I heard "actually, funny story that".

March 11, 2013 3:08 AM
 

David McKinney. said:

Who's Don Goggles?  Is he prone to nose bleeds!?

March 11, 2013 4:32 AM
 

Jason Horner said:

I'd like to subscribe to your newsletter... funny stuff

March 11, 2013 6:35 PM
 

Seb said:

Select all > delete

Please explain that.

March 12, 2013 1:33 AM
 

Ozzy said:

The "Select All > Delete" box means:

Ctrl + A --> Delete

or for Mac users:

Command + A --> Delete

I actually deployed my first triggers last month... :-o

March 15, 2013 6:00 AM
 

merrillaldrich said:

A bit more explanation on "select all > delete." What I meant there was, if the trigger cannot handle sets (or uses a cursor) those are generally such big problems that you have to throw away the trigger code and start over again. Hence select all (in your query editor) and delete.

April 16, 2013 6:36 PM

Leave a Comment

(required) 
(required) 
Submit

This Blog

Syndication

Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement