Re: Trigger Status Question
From: Scott Morris (bogus_at_bogus.com)
Date: 06/04/04
- Next message: stoko: "Re: Memory Cache Flushing"
- Previous message: ssovie: "RE: odbc"
- In reply to: Sean Newton: "Trigger Status Question"
- Next in thread: Eric.Li: "Re: Trigger Status Question"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 4 Jun 2004 14:41:49 -0400
IME - this is caused by tasks / scripts initiated and written by a user. I
would certainly suspect any scripts that wipe data from tables as this is
usually the reason for "temporarily" disabling them.
"Sean Newton" <sayno@spam.org> wrote in message
news:%23JU6k$lSEHA.3552@TK2MSFTNGP09.phx.gbl...
> What actions cause sql server 2000 to disable a trigger?
>
> We have noticed in our development environment that, for some unknown
> reason, our triggers become disabled.
> We are not altering table structures that I know of. We are occasionally
> doing a DELETE against all the tables to wipe it clean. There are some
> cascade deletes. I'm just trying to explain what we are doing when the
> triggers will occasionally stop working.
>
> When we rerun our trigger script (drop all the triggers, create them all
> again, enable RECURSIVE_TRIGGERS) everything works fine again. until we
> change a sproc here or there or do a wipe again. rerun script, works fine.
>
> Any ideas?
>
>
- Next message: stoko: "Re: Memory Cache Flushing"
- Previous message: ssovie: "RE: odbc"
- In reply to: Sean Newton: "Trigger Status Question"
- Next in thread: Eric.Li: "Re: Trigger Status Question"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|