Re: Creating a trigger program

-----Original message-----
From: CRPence CRPbottle@xxxxxxxxx
Date: Wed, 11 May 2011 15:41:03 -0500
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Creating a trigger program

On Wed 05-May-2011 11:59 , jmmckee wrote:

This may be a moot issue, however, as no matter how logical using a
trigger sounds, another person - not the sa in this case, is calling
the shots. His thinking is a batch job, run once a day, is good
enough.

FWiW, for a true "log file", I would most likely choose to perform
the additional work in a "log scrubber" whenever the actions can be
"batched overnight" [or on any schedule] versus whenever the actions
require more immediate action. A log file typically likely already will
have a scheduled process to trim unnecessary\outdated data [an effective
scrubber, but perhaps only for deleting rows], so adding a feature to
that existing process to handle the additional work of an email being
sent for certain rows can work well; esp. when there is a field that can
be changed to indicate the row has already been processed with the logic
and actions as performed by that added feature.

Regards, Chuck

Is is even easier than that, as the log file is copied to a Yesterday file, overwriting existing content. Original log file is then cleared. My thought was that the email message would not get sent until a little before 1AM, while the patient could well have been in the hospital since 2AM the previous day. It was probably more of a mind exercise. Doubtful is a doctor would come running just because one of his patients was admitted. Still, I did learn a lot, so it wasn't a wasted exercise - except, potentially for being a distraction to the truly great on this list.

Thanks all,

John McKee