Auditing Database 1

[JHeimall]

Does the auditing database have to be different from the CMS database?

Thanks!

 

[MJRBIM]

Yes, it can be on the same physical database server - but it is a totally different set of tables in a different database schema.

I usually name my database schemas something obvious to avoid confusion...

BOEXI_R2_PROD_AUDIT
BOEXI_R2_PROD_CMS

BOEXI_R2_DEV_AUDIT
BOEXI_R2_DEV_CMS

Depending on your volume of traffic, the size/number of BOE-XI services/processes you intend to audit, and the type of database you are using (eg. MySQL vs. ORACLE 10G) - you might want to put them on different physical database servers...but only if it's a very large BOE-XI install.

 

[groggle]

The other thing to remember about auditing in BOE XI is that the log files are written to a temporary file prior to being uploaded to the audit database. These temporary files are created on the default drive and default to a five minute lifespan. After five minutes these files are purged and uploaded to the audit database. An independent log file is kept for each BOE Server that you invoke the auditing facility for.

 

[Rivdog]

Hi,
I was advised by BOE support to create a different schema for the Auditing feature. What I couldn't get from BOE support was the minimum space requirements for Auditing on an Oracle database. They said it would vary depending upon how Auditing is set up. All I wanted was a minimum footprint sizing. Our DBAs like to know ahead of time, if possible, what are the space requirements. Has anyone installed auditing? If so, what is the size of the Auditing schema?
Thanks, Mike

 

[groggle]

A brand new Audit database with no history is in the order of 5MB. Quite small.

Typically 512MB to 1024 MB is sufficient for an ongoing Audit database depending on system size and usage.

As BO support suggest the long term size of the audit database is dependent upon how many items you set BOE to Audit, how many users are on your system and how many reports are run by your system.