It's true that's what they are for, but some shops and software companies (like the last one I worked at) prefer to avoid all the hassle that triggers involve when there are database changes. They were implementing a standard of using strictly SQL stored procedures for database processing (in and out, all changes). But as part of that process they began including an update to audit files for all of them as well, with the record written to it plus audit information.
When you move files that have triggers from development to QA to Production, it complicates things.
Alan
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Reeve
Sent: Wednesday, October 30, 2013 3:57 PM
To: Midrange Systems Technical Discussion
Subject: Re: Log file of file changes
If the file is journaled then just look at the journal receivers. That is about your only choice. FWIW - I disagree with your statement 'but that's not really what journaling isfor'......
A quick google search revealed the following - The primary function of journaling is to store record level database changes and allow those changes to be "rolled back" or undone, if needed. When a file is journaled, any changes at the record level are recorded to the journal first and are then applied to the database record. This is not to say that journaling will always be able to undo any changes that you've done to a file, but it does provide reasonably good protection and a good audit trail.
Warmest Regards,
Richard Reeve
On Wednesday, October 30, 2013 3:44 PM, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx> wrote:
All,
We had an issue recently about how a couple of prices got changed. The salesrep (who has _some_ control over pricing) says he didn't do it, and no one in the office remembers doing it. In fact, it was the sales rep who brought it up wanting to know what the %#@* is going on? :) By looking at month end backups, I know it happened sometime in August. Nothing like bringing it to our attention on a timely basis, right?
Anyway, in discussing it, the buying VP suggested a log file of changes. I think it's a great idea and it seems to me to be an ideal use for a trigger. Whenever a record is added/updated/deleted, just have the trigger write the record to this log file. It can have the same record layout as the file in question, plus add a few fields such as user and timestamp.
Seem reasonable? I've never written a trigger before but I can figure it out.
The file is currently journaled, but that's not really what journaling is for, IMO.
Thanks for any ideas.
--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com
The opinions expressed are my own and not necessarily the opinion of my company. Unless I say so.
--
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.
--
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.
--------------------------------------------------------------------------------
Confidentiality Notice: This email may contain confidential information or information covered under the Privacy Act, 5 USC 552(a), and/or the Health Insurance Portability and Accountability Act (PL 104-191) and its various implementing regulations and must be protected in accordance with those provisions. It contains information that is legally privileged, confidential or otherwise protected from use or disclosure. This e-mail message, including any attachments, is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. You, the recipient, are obligated to maintain it in a safe, secure and confidential manner. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Thank you.
--------------------------------------------------------------------------------
midrange.com
