The Control Compliance Suite relies on high performance from the production database. The database server that hosts the production database should meet the recommended specifications in addition to the minimum requirements. The evidence database and production database should be hosted on the same Microsoft SQL Server.
The production database server in a mainstream Control Compliance Suite deployment has the following specifications:
The production database server in a high-end Control Compliance Suite deployment has the following specifications:
The production database requires a large amount of free hard disk space. Further, you should dedicate the hard disks on the computer to individual tasks. Normally, you should configure the computer with multiple hard disks. All the disks should be high-speed, 15,000 RPM drives.
Potentially, the production database can grow very large. With 10,000 assets, the database size can exceed 50 GB. With 40,000 assets, the database can reach up to 200 GB. Regular maintenance of the production database can help regulate the database size.
One disk should be dedicated to host the computer operating system. One disk should be configured to host the computer swap file. The remaining disks should host the database files used by Microsoft SQL Server. For best performance, a SAN is recommended. If a SAN is not possible, the database should be stored in a RAID 10 arrangement.
For highest performance, consider configuring the database so that tables where a large amount of data is read or written are on a separate disk. Examples include the B_DataImports and R_CheckResults tables.
The computer that hosts the Production database should also be configured to use SSL connections to the Application Server. If you use SSL connections, you should configure them before you install the Control Compliance Suite.