Hi - We’ve recently had BI 4.1 implemented and we’re playing with it in a pre-production environment.
We’re using SQL Server to host the CMS and Auditing databases and one thing I’ve noticed is that the SQL Server Transaction Log for the audit database is HUGE.
It’s backed up daily and truncated however after 24hrs of the system sitting idling over (it still being pre-production with only a couple of users playing with it) the SQL Server transaction log is 90GB in size with the auditing events monitoring set to “minimal” in the CMC.
Only issue there is some audit reporting capability will be lost, obviously.
It may be worth performing further anlaysis to see what most of the entries are in the database. You could also try and isolate whther it is a SQL server issue, by switching to another database, for test purposes.
There is a confirmed bug when using the Audit database for the Monitoring Trending database. There is a KBA article on it but it is showing “Document is not released” right now. The KBA is 2014379 - BI 4.0 - Monitoring implementation on Audit DB leads to excessive redo logs. When we changed the monitoring back to using the default Derby database, we didn’t have this problem any more.
The KBA stated that this issue is fixed in:
BI Platform 4.1 SP 02 Patch 9
BI Platform 4.1 SP 03 Patch 4
(BOB member since 2007-08-17)
.