Manual Optimization
If your organization uses Microsoft SQL Server as the database engine and you store the file data in a file system folder (instead of the vault database), manually run the Optimize Database (Thorough) operation from one to four times a year. This is the only way to remove any destroyed files from the file data server in this type of setup. Run the operation also after an exceptionally large number of files have been destroyed at once, for example after files are archived to another vault.
Note: Make sure that the optimization is not done between file data
and metadata backups.
Note: It is possible that Firebird and Microsoft SQL Server
vaults are taken offline for the duration of the operation. Before you run the operation for Firebird vaults, make sure that the server has at least three times the amount
of hard disk space required by the metadata file of the vault. For instructions on how to check the
size of the vault metadata file, see Checking the Size of a Firebird Metadata File.
Note: Depending on the size of the vault, the
operation can take an extensive amount of time to complete.