Re: Do you test for the existence of a database trigger on a regular basis?

In our shop we don't disable the few triggers we have, but I can see why
that could be a worry for some folks.
That being the case, I think it would be easy to write a small program that
checks the systriggers table and informs if anything is amiss.

Best regards,
Luis Rodriguez

On Thu, Dec 11, 2014, 17:06 Glenn Gundermann <glenn.gundermann@xxxxxxxxx>
wrote:

Hi Folks,

I'm setting up some table triggers and associated trigger programs that
will create an interface table for another system.

Unlike a program that will error if a file is not journalled when required,
there isn't anything that will error if a table trigger is expected but is
missing or disabled.

I'm wondering if I should be creating a daily job to check. If the trigger
is not active, data will not get sent to the external system, and that
would be bad.

Is anyone checking if a trigger is still active or does everyone sleep
tight at night thinking everything is good?

Thank you in advance for any insights.

Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Cell: (416) 317-3144
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.