By: gosaveoption21

gosaveoption21 — Sun, 23 Jan 2005 10:30:59 +0000

Journaling on the 400 is only as good as the person or product that can scrum through the journal entries and decifer what the codes mean.
If your client is looking to merely satisfy an auditor “we’ve turned journaling on” is acceptable. The only thing they should watch out for is the next audit where the auditors ask for an example of how the changes are being tracked. Blank stares and a no-go on that part of the audit if they don’t have a product or program written in-house to give a list of changes.
You might want to ‘check out’ the PFs as a copy to make your changes and then run a query against the old copy (in production) and your modified copy. One word of warning though, if the client has a high availability solution in place this sort of change management might make it unhappy.
With SOX and all of the other standards creating an auditor feeding frenzy you should encourage your client to procure a product similar to datathread by innovatum (I don’t work for or use the product but saw them at Common last Spring)http://www.innovatum.com/datathread.php or develop a change management product like turnover. It might save them some fines and, if you are a reseller make you some money.

Comments on: Need a way to audit ANY change access to selected database files.

By: gosaveoption21