THE SQL Server Blog Spot on the Web
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
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 ;).
I sent this to the devs as soon as I saw it. Thanks!
Alex - there's a term for that. Let me think ... oh yeah, "success."
Thanks for lightening my day. I was just dealing with a stupid trigger on a client machine yesterday.
Merril - I don't quite understand the "Selet all > Delete" box. Could you please enlighten me?
This just made my day.
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.
Love it! How many times have I heard "actually, funny story that".
Who's Don Goggles? Is he prone to nose bleeds!?
I'd like to subscribe to your newsletter... funny stuff
Select all > delete
Please explain that.
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
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.