Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a custom trigger on a 3rd party app table to help us audit changes. Occasionally that trigger is removed. Looking thru the traces it shows that the 3rd party app is dropping it (for no good reason). The Vendor acknowledges it does this "from time to time" to ensure that no one mucks with their database and is not willing to change their app (understandable).

Okay, I get this, but we really need that trigger. Is there a way to disable drop trigger to their app login for this table/trigger? I can't deny ALTER on the database because their app does create/drop tables. Thanks!

share|improve this question
up vote 2 down vote accepted

There's no way to do that, but you might be able to create a ON SERVER or ON DATABASE DDL trigger that recreates the trigger after their software drops it.

More info on DDL triggers:

share|improve this answer
Not perfect but I think I can work with it from there. THANKS! – Matt Rogish Dec 30 '09 at 22:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.