Shrinking Security Center databases after an upgrade - Security Center 5.7

Security Center Administrator Guide 5.7

Applies to
Security Center 5.7
Last updated
Content type
Guides > Administrator guides
English (United States)
Security Center

After a database upgrade, its disk usage may significantly increase due to the temporary storage required to execute the upgrade transactions. The disk space used during the upgrade is not automatically released after the upgrade is complete. To reclaim the unused disk space, you must shrink the database.

Before you begin

Not all database upgrades cause the database to grow in size. However, in the case of the Archiver database upgrade from 5.3 to 5.7, we do recommend shrinking the database after the upgrade. If you are not sure whether or not you need to shrink your database after an upgrade, check its disk usage with SQL Server Management Studio.

What you should know

Depending on the recovery model of your database, a transaction log backup may be required in order to reclaim the unused disk space. For more information, see the following online articles: Recovery Models (SQL Server) and Transaction Log Truncation.


  1. Follow the procedure Shrink a Database published online by Microsoft.
  2. Apply the same procedure to all databases that require shrinking.