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

[Bruce Vining <bvining@xxxxxxxxxxxxxxx>]

I have code that checks, among other thing, for required triggers every
night. If possible it adds any missing triggers, if not possible it sends a
message to QSECOFR notifying them of the problem.

Bruce Vining


On Thu, Dec 11, 2014 at 3:36 PM, 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.