How to calculate SiteProtector Database utilization for purging data when emergency purge is enabled
How is the SiteProtector Database utilization calculated for purging the data when emergency purge is enabled?
The SiteProtector Database can be configured in two ways and the database utilization calculation differs in both the cases. Both scenarios are listed below:
- The database can be configured with restricted file growth with a maximum database size. Below is the calculation in this scenario:
- Current database space used/maximum database size = % utilization
- For example, say that you have the SiteProtector database that is configured with Max DB Size of 10 GB and currently the database is using 1 GB. This would mean that the database is 10% full.
- The database can also be configured to have unrestricted file growth. Below is the calculation in this scenario:
- Total allocated space + available space on disk = maximum database size
- Total used space/maximum database size = % utilization
- For example, say that the database is using 10 GB on a 100 GB drive with 20 GB of free disk space. You allocated 15 GB to the database when this was first created. Below are the calculation:
- 15 GB allocated + 20 GB available space on the disk = 35 GB maximum database size
- 15 GB used / 35 GB maximum database size = 43% full
There is a SQL stored procedure that is called iss_CheckDataSpace, which can be manually run through SQL Management Studio or through command line, which does this calculation for you. The TotalPercentofMax column value is used for emergency purges and other health checks.
Translate this page: