After archiving and/or purging events, the database is still the same size (4238073)

After archiving and/or purging events, the database is still the same size

After setting up an archive or purge job to delete older events from the Change Auditor database, the size of the database does not appear to change.  There may be many reasons for needing to purge out events, but usually it is due to needing to recover disk space on the SQL server.

When events are purged from the Change Auditor database, SQL frees ups space within the database file, but doesn't reduce the size of the database file on the disk.  This new empty space is referred to as "white-space" in the database file.  This can be viewed in the SQL Server Management Studio by right clicking on the Change Auditor database, and selecting Properties.  On the General tab, the total size on disk will be listed next to the "Size" field, while the available space, or white-space, is listed as "Space Available."

If left alone, the SQL Server will place new information into the white-space as new events are generated and added to the database.  Only after the white-space is used up will the database file grow.

If desired, a SHRINK task can be run against the database to reduce the size on disk by removing some of the white-space.  Quest will ultimately defer to local DBAs and/or Microsoft Support with regards to best practices surrounding running the SHRINK task.