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

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

See Trimming the FSA Reporting database history tables

FSA Reporting also includes an SQL purging job that moves old data from a 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.

The purging job's move operation can take from one minute to a number of hours for a large database 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 9.00 P.M. You can change this schedule if required.

See Changing the schedule for an FSA Reporting database purging job

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

See Running the FSA Reporting database purging job manually

See About the FSA Reporting databases

See Maintaining the FSA Reporting databases

See About Enterprise Vault Reporting

See About Enterprise Vault Reporting's reports

See How Enterprise Vault Reporting works

See How FSA Reporting works

See About the FSA Reporting proxy servers for non-Windows file servers

See Implementing Enterprise Vault Reporting