Logging Table Changes

[KMoody]

Progress: 10.2b SP7
OpenEdge Architect: 3.4.2.R342_v20090122-9I96EiWElHi8lheoJKJIvhM3JfVsYbRrgVIWL
OpenEdge OS: Windows 7 Professional 2009 SP1

We need to keep a log of our users' changes to tables and fields. Specifically, we need:

• to select which tables and fields to log,
• to log who made the changes, and
• to log the field values before and after the changes.

Is there a way to do this in the OpenEdge logging infrastructure? Should I use table and field triggers or auditing instead?

 

[TheMadDBA]

Use Auditing instead. It will be far less painful than worrying about table/field triggers. Documentation for Auditing is in the Core Business Services PDF and is fairly straight forward, especially if you are already setting the Progress userid for all of your connections.

I don't think you can accomplish this with the logging/log manager functions.

 

[Cringer]

OE Auditing is the bee's knees for this. Just make sure you have a strategy for archiving etc BEFORE you enable anything. There's quite a few presentations on Auditing in the communities so take a look. Here's a case study to get you started: http://www.pugchallenge.eu/images/2014pdfs/mike_furgal_audittrails.pptx

 

[Rob Fitzpatrick]

Use Auditing instead.

Just make sure you have a strategy for archiving etc BEFORE you enable anything.

Absolutely agree with both. Your needs are precisely matched by OE Auditing's capabilities. I strongly suggest that if you go this route, you create a separate audit archive database and do your audit querying in it instead of in production. Understand that you will need to assign certain auditing roles to privileged users, e.g. Audit Administrator, Audit Data Reporter, and Audit Data Archiver.

For more information and guidance, read this thread.

 

[KMoody]

Thanks! The more I learn about auditing in OpenEdge, the more I like it.