Business Objects Auditing Database

[Former Member]

Hi,

Is there any way to filter events in the auditing database for a particular user, so that these events are not written to the audit database?

Also, in terms of the management of the auditing database, i.e. purging old data, truncating, setting constraints etc, are there any do's and dont's around this or is at the discretion of the dba?

Thanks

[amrsalem1983 · Accepted solution]

those are the audit database tables

APPLICATION_TYPE

AUDIT_DETAIL

AUDIT_EVENT

DETAIL_TYPE

EVENT_TYPE

SERVER_PROCESS

all of them are master table except the AUDIT_DETAIL,AUDIT_EVENT

which is variable transaction tables.

you are not allowed to delete or update those tables while the CMS is running

when you want to delete any old data stop the CMS, then delete from AUDIT_DETAIL,AUDIT_EVENT

based on START_TIMESTAMP between the specific dates.

i dont think can audit actions by a specific user, but you can audit actions based on services,

like if you want to audit the WebI reports only,

you will find those options in the CMC, in the properties of every service,

click Servers, then the server you want to audit, then go to the Audit tab, and select the actions you want to audit.

good Luck

Amr

[Former Member]

Benjamin,

The questions that you have are best answered by contacting your Business Objects sales representative and requesting information about the BusinessObjects Enterprise Sizing Guide. Your sales rep in turn should put you in contact with a Business Objects Professional Services Consultant who can then assess your reporting environment and assist you in

sizing these services appropriately for you.

Thanks,

John

[Former Member]

Does BO Auditor impact performance on BOXIR2 Enterprise. If there are lots of users constantly accessing BOXI will the auditing of these events slow down the performance to Enterprise? If so how much is performance affected 5% 25% 50% ??????

[Former Member]

Generally speaking, indexes can help in certain situations in regards to speeding up queries. On the downside, indexes may slow down update/add operations, so the answer is, it depends. The Auditor database is transactional in nature, however, it gets data loads at specified intervals (the default is once every 60 minutes), so being that updates would theoretically get 59 minutes to process before the next batch comes in, then an index shouldn't become a problem. If the specified interval is reset to something less, then the build or no-build of indexes should be reconsidered.

Thanks,

John

[Former Member]

Is it a good idea to put indexes on these audit_event and audit_detail tables or will this affect the writing of the log files to the database

[Former Member]

Benjamin:

Also, in terms of the management of the auditing database, i.e. purging old data, truncating, setting constraints etc, are there any do's and dont's around this or is at the discretion of the dba?

Purging or truncating data: this requires understanding the data model. There are two tables that are transactional in nature (audit_detail & audit_event). If you delete data from one, then you should also delete data from other at or about the same time. Here is an SQL statement for deleting (note, change the date values accordingly, this snip-it deletes all 2007 data...

delete from audit_detail 
  where audit_detail.event_id+server_cuid in ( 
     select event_id+server_cuid from audit_event 
         where convert(char(11),start_timestamp,112) 
       between '20070101' and '20071230') 

delete from audit_event where convert(char(11),start_timestamp,112) 
       between '20070101' and '20071230'

Setting constraints: I would not recommend doing this as BOE populates the two transactional data using its own methodolgies. You shouldn't have trouble making the relationships work properly in any free-hand SQL you apply. Even though integrity constraint is not enforced via PK/FK connections, BOE is tight with what it is doing...

Thanks,

John