About Auditing

Auditing enables information to be collected about data models downloaded from the repository. You can use auditing features to track how long queries take to process , which tables and columns are used most often, and even record the full SQL statement that is sent to the database.

Audit information can help the database administrator monitor not only the effectiveness of each distributed data model, but also the weaknesses and stress points within a database. The results are useful for performing impact analysis to better plan changes to the database.

Auditing requires minimal additional setup and can be implemented entirely within the studio version of Interactive Reporting. The steps required for auditing data models are:

Create a document repository with an inventory of distributed data models.
Create a database table in which to log audit events.
Use data model options to define events that you want to audit for each data model.
Save the audited data models to the document repository.
Use Interactive Reporting to query the audit table and to analyze the data it contains.

Special Considerations

The Audit log may fill up. Monitor it regularly and delete any entries that are no longer used.
Before uploading your audited data model to the document repository, log in as a user and test each auditing event to verify that your SQL statements are not generating any errors.
Auditing is not supported for the Process Results To Database Table feature, nor for data models. However, scheduled Interactive Reporting documents containing linked data models are audited normally.