About the FSA Reporting database

When you configure FSA Reporting, Enterprise Vault creates the FSA Reporting database with the following component names:

Database name

EnterpriseVaultFSAReporting

Data device name

EnterpriseVaultFSAReporting_Data

Log device name

EnterpriseVaultFSAReporting_Log

The initial size of the FSA Reporting database is as follows:

Data device

100 MB

Transaction log

80 MB

Total

180 MB

You must trim the FSA Reporting database regularly to keep its history tables at manageable size, while retaining recent and trend-related information. Enterprise Vault provides a utility for this purpose. The trimming utility removes data beyond a specified age, but it retains the data for the trend reports.

From Enterprise Vault 8.0 SP3 onwards, FSA Reporting also includes an SQL purging job that moves old data from the database's main tables to its history tables. The purging job helps to keep the main tables at a reasonable size, which enables FSA Reporting to generate its reports quickly.

Note:

The purging job only purges data from the main tables to the history tables. You must run the trimming utility regularly to trim the history tables.

The purging job's move operation can take from one minute to a number of hours for a large system with a lot of data to move. Enterprise Vault places the FSA Reporting database into purging job maintenance mode while it performs the SQL move operation. The FSA Reporting Web service suspends the upload of data to the database while the database is in purging job maintenance mode, unless a timeout period is exceeded.

By default the FSA Reporting database purging job runs daily at midnight. You can change this schedule if required.

You can run the purging job manually, if for some reason the job does not run automatically for some time.

More Information

Trimming the FSA Reporting database history tables

Changing the schedule for the FSA Reporting database purging job

Running the FSA Reporting database purging job manually