This tip helped me think of a way to overcome a problem I've been having with instead of triggers defined on views. If the view gets dropped, so does the trigger. This is good when you really want to delete the view. However, a common way to edit a view is with drop view and create view, which will delete the trigger as well. Enterprise Manager (2000 SP4) will make sure to preserve triggers on tables when table design changes are made which drop the and re-create the table, but it doesn't do the same with views. It's difficult to remember to not edit these views with Enterprise Manager or by using the Create option in Query Analyzer.

So, I'm going to try this technique to protect the views on which I have created triggers for my application.

Thanks for keeping the older articles on here!

DAN9/25/2006 2:29:16 PM