Re: Audit Trail?

> Our application requires us to keep a human-readable audit trail of > every modification to our database (the Informix version doesn't exist > yet -- we're converting from isam files). So far the only thing we > know to do is to put insert, update, and delete triggers on every > table in the database to log each change. > > In the isam world, we use the logs for three reasons: to allow > recovery after a system crash, to provide auditability, and for > debugging purposes. Informix handles the first case for us, but how > can we handle the other two without resorting to the triggers > mentioned above? One of the real drawbacks of a delete trigger is that > according to the Informix manuals it prevents use of a cascading > delete process. > > Surely we're not the only site that requires such accounting. Has > anybody else come up with something better, or is there something in > the engine itself that we have overlooked? > > Thanks for your suggestions, > M. Livenspargar > You don't say if you are using OnLine or SE. In Online there is a utility program called tblog which could provide the information you need, albeit in hexadecimal dump format. Malcolm Weallans Online Database Consultancy Phone 01628-72154 Fax 01628-37463 CIX - onlinedbc