A Control Compliance Suite (CCS) user installing the product can choose to create the CSM_DB and the CSM_Reports databases manually rather than let the product create the databases.
This document will cover certain facts and guidelines for manual database creation. When a database is created by the installer the database is a copy of the model database with some exceptions.
The following are the considerations for manual database creation:
· Support for custom database names does not exist.
· The default file group of the CCS databases must be PRIMARY.
o CCS continues to use the PRIMARY file group even if the default file group on the CCS databases is set to a user defined file group.
· For manually created databases, the Application Server Service account must have the DBO privilege on CSM_DB and CSM_Reports. SYSADMIN privilege is not required once the databases are created - DBO is sufficient.
· Initial database size of 1024 MB is recommended for both CSM_DB and CSM_Reports.
· The growth of the databases is based on the following factors
o Number of assets in the system
o Frequency of evaluation of standards against assets
o Evaluation results
o Purge criteria
Indicative scaling guidelines for the CCS databases can be found in the Online Help.
Best practices around database growth settings can be found at KB:
· If the user wishes to have multiple database files, it is recommended that addition of the same is done post the installation of the product.
· Recovery model of CSM_DB is set to Full.
· CSM_DB has two file groups
o PRIMARY (Default)
§ Autogrowth – 1 MB, unrestricted
o CCS_QUERIES – Used to store Queries data.
§ Initial Size – 50 MB
§ Autogrowth – 10%, unrestricted
Following are the database properties post installation:
· Recovery model of CSM_Reports is explicitly set to Simple.
· CSM_Reports has two file groups
o PRIMARY (Default)
§ Autogrowth – 1 MB, unrestricted
o CSM_Reports_EvidenceStorage_%DATE% – Used to store Evidence data.
§ Initial Size – 100 MB
§ Autogrowth – 100%, unrestricted