Control on Auditing Database (Data)

[system]

Tannx,

How can you achieve database trigger.

A trigger is a function available to you dependent upon your RDBMS vendor – check your documentation for availability and syntax.

BO database data is in blob format.

Not every implementation is using a BLOB (Binary Large Object) type, for example I’m using SQL Server and we have nvarchar(255) in use, which in other implementation may become a BLOB…

Anyhow, Nick Daniels’ suggestion for a trigger may work, technically, however, in some implementations, the DBA may not want to entertain this type of trigger that would check for instances over three months when an insert operation occurs, especially since Auditor may insert data once every 15 minutes per day – it may be too much overhead to bear. Another approach might be to have a monthly run executed manually each month. Most DBAs have weekly and monthly chores, so adding this to their “to-do” list may not be too much of a problem. If you’d like to see such an example of running a SQL command to trim down the Auditor database using a date factor against the Start_Timestamp, have a look at this thread:

120×120 10.4 KB

Hi, We have a requirement. We are running BOE XI R2. We want to keep only the last 3 months data in the Audit database. We want to regularly cleanup the data which are more than 3 months old. Could anybody shed some light on how to acheive this? Your help is much appreciated. Thanks. The Boss (BOB member since 2008-02-08)

Thanks,
John

---

jsanzone (BOB member since 2006-09-12)