Sizing guidelines

Secure Private Access on-premises databases

The Secure Private Access on-premises database contains information about the applications, policies, and related artwork. It also contains information related to troubleshooting and telemetry.

Due to their dynamic nature, the records for telemetry and troubleshooting undergo frequent changes and are kept for a short period. Therefore, a Secure Private Access on-premises database must be configured considering the need for frequent updates.

During internal scalability testing, the following configuration of Secure Private Access on-premises database was able to handle a 5000-user load.

Component Specification
Processor 8 vCPU
Memory 16 GB
Network 10 GBPs networking
Host storage

Size: 127 GB
IOPS: 500
Maximum throughput: 100
Operating system Windows Server 2022
SQL Server SQL Server 2022 CU12
Daily database space used for 5000 users 5 GB

Note:

  • The metrics are derived based on the assumption that the log event cleanup is disabled and the log retention period is set to 7 days.
  • By default, the logs are retained for 90 days or up to 100 K log events are retained depending on the configured settings. These settings are available in the Secure Private Access Runtime service appsettings.json file and can be modified as required. For details, see Settings to retain event logs.

Decision server sizing

The scalability of Secure Private Access on-premises server depends on the database used. The database stores telemetry and troubleshooting information. The database’s scale depends on memory, disk speed, and the number of CPUs used to process the load.

During the internal scalability testing, it was confirmed that the following configuration of 3 Secure Private Access on-premises nodes was able to handle a 5000-user load.

Component Specification
Processor 4 vCPU
Memory 8 GB
Network 10 GBPs
Host storage


Premium SSD LRS
Size: 127 GB
IOPS: 500
Maximum throughput: 100
Operating system Windows Server 2022
Sizing guidelines