Worksoft Database Server System Requirements
When configuring your database server, you must estimate how large your databases will become by figuring out usage. To help you determine your hardware requirements, Worksoft has provided the three following types of usage models:
|
Usage Model |
Number of Users Creating Certify Processes |
Usage |
|
Light |
Up to 10 users |
Generate a small number of processes with a low volume of test results weekly. |
|
Medium |
10 to 20 users |
Generate a higher number of processes with a moderate and increasing volume of test results daily. |
|
High |
10 to 20 users (or more) |
Generate a very high number of processes with a high and increasing volume of test results daily. |
Light Usage Model
This usage model is the typical starting point for most Worksoft customers. If you are starting with more than 10 users, your usage may quickly outgrow the Light Usage model. In that case, follow the Medium Usage model recommendations.
The requirements for the Light Usage model are based on the following assumptions:
- Nightly execution has not been established yet because the test automation is still being built.
- Results maintenance is implemented with Certify SQL maintenance jobs once regular process execution has begun.
- Screenshots are only taken on a failed process step or a specific step.
Medium Usage Model
The primary reason for choosing this model is the number of processes and executions you expect to be running on a daily basis.
The requirements for the Medium Usage model are based on the following assumptions:
- Certify process execution is done daily across 50 virtual machines, and 700 transactional Certify processes are executed continuously for 8 hours.
- Results maintenance is implemented with a Certify SQL maintenance job to archive and delete results.
- Screenshots are only taken on a failed process step or a specific step.
High Usage Model
You should implement the High Usage model if you have 10 or more concurrent users creating test processes with Certify and executing a large number of processes nightly to account for future growth.
The requirements for the High Usage model are based on the following assumptions:
- Certify process execution is done daily across 120+ virtual machines, and 1,500 top-level Certify processes are executed continuously for 8 hours.
- Results maintenance is implemented with a Certify SQL maintenance job to archive and delete results.
- Screenshots are only taken on a failed process step or a specific step.
System Requirements
Listed below are the system requirements for the database server for each usage model.
|
Usage Model |
Supported Database Servers |
CPU |
RAM |
Database Space |
Required Third-Party Software |
|
Light |
|
8 processor cores 2.0 GHz |
16 GB |
50 GB |
Microsoft .NET Framework v4.5 (for running Certify database scripts) |
|
Medium |
|
8 processor cores 2.0 GHz |
16 GB |
100 GB |
Microsoft .NET Framework v4.5 (for running Certify database scripts) |
|
High |
|
16 processor cores 2.0 GHz |
32 GB |
500 GB |
Microsoft .NET Framework v4.5 (for running Certify database scripts) |
*Performance can be slow while upgrading or creating a new database on SQL Server 2022.
A SQL Server database administrator is recommended for professional planning and maintenance.
Worksoft does not support Microsoft Azure’s Managed Identity feature for enabling the configuration of SQL Server databases.
SQL Server Collation Requirement
Worksoft Certify requires the following for SQL Server Collation:
-
Character set to be ASCII equivalent.
Example: Latin1
- Code Page 1252 (CP1).
Worksoft Certify supports both case sensitive (CS) and case insensitive (CI), and it is accent sensitive (AS).
Example : SQL_Latin1_General_CP1_CI_AS
SQL Server Mixed Authentication Mode
When setting up a Certify Database, it is recommended that you select Mixed Authentication Mode during your SQL Server configuration. Mixed Mode enables both Windows and SQL Server authentication.
Worksoft recommends Mixed Mode for the following benefits:
- Only one database logon user is necessary
- User ID and password are encrypted in the Certify configuration
Related Topics