better auditing (maybe)

[kdhadmin]

we are just starting out using Sugar pro, and I'm researching all the various options and tools available to us.

I've now started looking at auditing, because this is a big concern of ours with any of our systems, not just sugar.

one of the questions i've seen repeated in these forums, is wanting to audit more than is readily available to audit with the 'stock' sugar.

so, onto my thread subject - why not have the database engine do the auditing ?

I've set this up before, with other systems using MSSQL.

[jmertic]

You could very well do this by turning on the MySQL query log, but the data is quite difficult to parse.

That said, you can make any field in Sugar audit-able; what other auditing are you looking for?

[kdhadmin]

basically, I want to audit ALL changes. I realize this is a LOT of data to store, but sometimes this is necessary.

also, I don't want to go and code each field with a vardefs.php, that would be time consuming, and I might miss fields, especially future custom fields.

what I was thinking was something along the lines of triggers in the database, which would take care of all the fields. and this trigger-audit could record to the sugar audit tables, and therefore would not rely on MySQL query log.

looking for anyone's input on this as to why it would be a bad idea ....


(we are a small-medium company with about 25 sugar users and maybe 7,500 customers)