You can use the following table to help you determine the total storage size based on the number of endpoints.

File Type Size per 1,000 endpoints For deployments under 5,000 endpoints Size per 1,000 endpoints For deployments between 5,000 and 10,000 endpoints Size per 1,000 endpointsFor deployments over 10,000 endpoints Note 2
Data 90 GB 55 GB 20 GB
Index 50 GB 25 GB 20 GB Note 1
Log 50 GB 25 GB 10 GB
Temp 35 GB 15 GB 5 GB
Total 225 GB 120 GB 55 GB
Note:

  • 1: Flash PCIe storage is required for Index files for deployments over 10,000 endpoints

  • 2: SQL database deployments over 10K endpoints requires SQL Server Enterprise. The figures in the table assume use of database compression.

Database size is calculated differently for different deployment sizes for two major reasons:

  1. SQL Server Standard edition prior to SQL Server 2016 SP1 does not provide SQL database compression.
  2. Some SQL tables grow in a non-linear way.

You can pro-rate this data for desired table size.

Here are few examples of how you would use this data to determine your database size:

Example 1. Deploying App Control server for 8,000 endpoints

  1. According to the OER, a single DAS partition is needed for 8,000 endpoints.
  2. In the table, the guidelines for 8000 end points are in the second column (5,000 – 10,000 endpoints).
  3. Based on the table guidelines, the total storage needed is 120 GB ´ 8 = 960 GB

Example 2. Deploying App Control server for 30,000 endpoints

We will calculate the storage needed for 30,000 endpoints by referring to the table titled App Control Server Architecture by Endpoint Count from the OER and to the database size calculator above.

  1. According to the OER table, one DAS partition and a second partition on PCIe flash storage are needed for 30,000 endpoints.
  2. We must prorate the values from the OER table. Dividing 30,000 endpoints by 40,000 gives a factor of 0.75. The OER table indicates that 2 TB would be needed for 40,000 endpoints. Thus, 1.5 TB in total would be needed for a 30,000 endpoint deployment.
  3. In the calculator table above, the third column (deployments over 10,000 endpoints) provides the guidelines for 30,000 endpoints. To get the values we need for the index file for 30,000 endpoints, we calculate 20 GB ´ (30,000 endpoints / 1,000 endpoints) giving us 600 GB for index storage.
  4. Since the rest of the database (Data+Log+Temp) needs to go to the DAS storage, we will calculate the prorated size required as we want 1. 5 TB – 600 GB = 1,536 GB – 600 GB = 936 GB for the remaining storage.

Example 3. Deploying App Control server for 100,000 endpoints with maximum performance

We will calculate the storage needed by referring to the table titled App Control Server Architecture by Endpoint Count from the OER and to the database size calculator above.

  1. According to the OER table, one DAS partition and second partition on PCIe flash storage are needed for 80,000 endpoints. For maximum performance, however, the OER also recommends putting the entire database, except for the Log files, on the PCI storage.
  2. In the database size calculator table, the third column provides the guidelines for 100,000 endpoints. The log files, which need to go into DAS storage, will have a size of 10 GB ´ (100,000 / 1,000) = 1,000 GB = 0.98 TB
  3. The remaining files (data, temp, and index) must go on flash storage. We prorate the values in the OER table by multiplying by 100,000 / 80,000 = 1.2.
  4. The OER table indicates that the total database size is 4 TB. Prorating gives 4 TB ´ 1.2 = 4.8 TB.
  5. The storage required on flash storage is thus 4.8 TB – 0.98 TB = 3.8 TB.