Impact on the DB to enable the audit log?

[Guillaume]

Hi,

I'm running a large EA project that shared via Ms SQL Server (coupled with SVN). As I recently had to identify how parts of the model disappeared (deleted by a user), I used the Baseline compare feature with older versions of the XML files, retrieved from SVN.

I think EA auditing would provide me with finer grained results, hence I'm considering enabling this feature. However due to the amount of extra data to be stored, can anyone share any experience in the long run ?
Should the audit be cleared on a regular basis or can it be kept ? Should it be stored as a backup in a different table or DB?

Thanks

[qwerty]

As long as you don't turn on the XML im-/export logging it's no issue at all. Remember that it only stores manual changes per modeler. Assume that over the day there are one change per 5 minutes (which is definitely a too high volume since in that case the modeler did not *think* between changes) you end up with 8*60/5 = 96 changes per working day and modeler or 19200 records per year (200 working days). Now multiply that with the number of modelers you have. That's not a number any DB admin would be afraid of.

q.

[RoyC]

You can save Auditing data in log files. Keeping the log files within the project can slow down navigation of the Project Browser and loading/changing modes in the Audit View. However, you can write out the log files to a file location external to the project, and reload them as you need them later. It's no big deal either.

[Guillaume]

Hi Roy,

Could you provide me with details on how to export audit log files, and loading them when needed? (EA command, script?)

Thanks

[qwerty]

Repository.SaveAuditLogs (string FilePath, DateTime StartDateTime, DateTime EndDateTime)

Project/Auditing/Audit Settings

q.