Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
dhw
Constraint Violating Yak Guru
332 Posts |
Posted - 2005-07-18 : 14:54:09
|
Hello...I have an Insert trigger on a table...that has been there for over a year...and this morning a bug occured that was caused by the fact that the table's Insert trigger was no longer present. Has anyone experienced anything like this before?thanks for any help. - wd |
|
Thrasymachus
Constraint Violating Yak Guru
483 Posts |
Posted - 2005-07-18 : 14:59:03
|
who else has access enough to drop triggers?anyone run any routines that disable them?things do not generally go poof.Sean RoussyPlease backup all of your databases including master, msdb and model on a regular basis. I am tired of telling people they are screwed. The job you save may be your own.I am available for consulting work. Just email me through the forum. |
 |
|
dhw
Constraint Violating Yak Guru
332 Posts |
Posted - 2005-07-18 : 15:18:21
|
There are three other devs with access...but really no motivation or interest in dropping the triggers.No other routines or functions that run that would disable them. The only regular process that runs is the daily backup of the database. |
 |
|
Bustaz Kool
Master Smack Fu Yak Hacker
1834 Posts |
Posted - 2005-07-18 : 15:55:45
|
"but really no motivation or interest in dropping the triggers"Sometimes the worst "hackers" are ourselves when we do something accidentally. Was anyone doing anything with the table recently?HTH=================================================================The most tyrannical of governments are those which make crimes of opinions, for everyone has an inalienable right to his thoughts. -Baruch Spinoza, philosopher (1632-1677) |
 |
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-07-18 : 19:58:00
|
if you have not removed the BUILTIN\Administrators group from your instance, anyone who has local admin on your server also has SA privs in your databases.Chances are it was someone who accidentally deleted the trigger and doesn't want to own up to it. Maybe they thought they were working on DEV/TEST, but in reality they were working on your production database.-ec |
 |
|
dhw
Constraint Violating Yak Guru
332 Posts |
Posted - 2005-07-18 : 20:03:46
|
Good points about someone accidently deleting them. That is the only thing I can think of at this point. And, the fact that we do have a Dev Database on the same server.....makes me wonder if someone did do some work on that table in the production DB and assumed that they were working in the Dev DB and somehow dropped the trigger. |
 |
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-07-18 : 21:23:55
|
an instance is when altering the table, this drops all triggers on that table in order to save the changesquote: Originally posted by dhw Good points about someone accidently deleting them. That is the only thing I can think of at this point. And, the fact that we do have a Dev Database on the same server.....makes me wonder if someone did do some work on that table in the production DB and assumed that they were working in the Dev DB and somehow dropped the trigger.
--------------------keeping it simple... |
 |
|
|
|
|