SQL Server Trigger Dissapears
Posted on 2014-04-16
I have an ongoing issue where an insert trigger dissapears from a DB after its first execution. The trigger is supposed to calculate some information and the insert a record into a separate table. Currently, the trigger fires, calculates the data, inserts the record into the appropriate table, and then dissapears completely from the DB.
We've never had this issue in any other DB and we have the trigger installed in countless other sites; so it seems to be an environmental thing.
Does anybody know of a situtation where a trigger would be dropped automatically by SQL Server due to an issue during execution or anything else?
Very broad question, but I'm running out of things to try.