Disk sizing for Reporting database

The disk size that a SQL server computer hosting reporting database requires, depends on the following variables:
  • Number of assets in the system
  • Number of standards in the system
  • Frequency of evaluation of a standard against number of assets
  • Evaluation results
To determine disk requirements for SQL server computer hosting reporting database, the following guidelines should be followed:
No. of assets*No. of checks*constant 3.5 * No. of iterations =Size in KB
The disk requirements for SQL server computer hosting reporting database depends on the frequency of scans.
Disk sizing for the Reporting database considering weekly scan
Number of assets
Approximate database size after one scan for 350 checks (GB)
Approximate increase in a month for database size assuming weekly scan(GB)
Approximate disk space needed for 1 year of usage (GB)
1000
2
8
100
5000
6
24
300
10000
12
50
600
30000
36
150
1800
100000
120
500
6000
Disk sizing for the Reporting database considering monthly scan
Number of assets
Approximate database size after one scan for 350 checks (GB)
Approximate increase in a month for database size assuming monthly scan (GB)
Approximate disk space needed for 1 year of usage (GB)
1000
2
2
25
5000
6
6
80
10000
12
12
150
30000
36
36
450
100000
120
120
1500
Disk sizing for the Reporting database considering quarterly scan
Number of assets
Approximate database size after one scan for 350 checks (GB)
Approximate increase in a month for database size assuming quarterly scan (GB)
Approximate disk space needed for 1 year of usage (GB)
1000
2
1
8
5000
6
2
24
10000
12
4
50
30000
36
13
150
100000
120
40
500
The above database size recommendations are for one year. For 3 years of usage, disk space can be increased linearly. Reporting database purge criterion is 3 years by default.
The above disk sizing requirements are estimated for Windows assets. For other platforms, the disk size may vary due to increase in evidence size and type of evidence ( positive / negative).