Ok, this post probably won't be as good as the one that just got lost into cyberspace, but I'll try to sum up the main points:

I typically attack this issue...

just spent 20 minutes on a writeup in here and when posting the message, it didn't take, so I'm testing this out before I rewrite the whole thing again...

please disregard,...

Actually, this topic got me thinking of another really bad practice along the lines of "object qualification".  Perhaps this is not the thread for this discussion, but I'd be curious...

(dwebb) - That really is the question.  As (bozo7) put it, it seems as though most people do not take advantage of multiple ownership of objects, which, based on my experience, I...

"The "correct" answer clearly states that the deleted table holds the reocrds ABOUT to be deleted.  Since a trigger is fired AFTER the SQL statement executes, the would hold the...

Ok, Ok, thank you all.  I'm just going to keep my mouth shut now.  I actually had to go back and verify it for myself, and yes, I am wrong.

Even...

Yes, this trigger stopped me in my tracks for many reasons.  The biggest of which is that I've NEVER EVER seen a single trigger written for INSERT, UPDATE, and DELETE...

Actually, after relooking through the posts, one could deduce that an error would be generated, although the error would have been generated when the insert trigger was created (due to...

The real problem with this question is the fact that "No row will be inserted" is not exactly correct although definitely pliable.  While we can most definitely deduce that the...

Thanks for the reply.

Yup, I know that encryption is easily breakable, however it does provide a "front line" against the casual observer going in an messing with it. When...

a few gotchas I've run into in the field:

Joining inserted to deleted (for multirow compatibility) is indeed a good idea as long as you do NOT allow updates to your...

A couple of little things I can think of:

* big distribution database (are your distribution cleanup jobs working). If msrepl_commands gets really big, I've known replication...

more to the point on logs... I'm pretty keen on xp_logevent, as it doesn't cause replication to blow up (like raiserror) and you don't have to create a table for...

Of course, there's always SQL-DMO. You could always "build" your own EM using it. It really depends on what you want to do with it.

One thing I can offer from having done some of this: it can get a little tricky, depending on what your "batch job" actually is. I believe that...