Deploy a second Collection Server when you need to audit separate homogeneous environments of SQL Server instances, such as a SQL Server 2005 environment and a SQL Server 2008 environment. For example, you could deploy one Collection Server to dedicated SQL Server 2005 instance in one environment and a second Collection Server to a dedicated SQL Server 2008 instance in another environment. Use the following checklist and instructions to successfully deploy a second Collection Server.

Deployment checklist

Follow these steps ...

Determine whether you want to upgrade to the latest version of SQL Compliance Manager. To verify whether you are running the latest version, click Check for Updates on the Help menu.

Choose the appropriate upgrade strategy for your environment and your auditing needs.

Ensure the computer that will host the new Collection Server:

  • Has trusted access to the computers hosting the SQL Server instances you want to audit.
  • Hosts the same version of SQL Server as the upgraded instances. For example, if some instances were recently upgraded to SQL Server 2008, install the Collection Server on computer hosting SQL Server 2008.
  • Meets the product hardware, software, and permissions requirements.

Deploy new Collection Server after the SQL Server on an audited instance has been upgraded

  1. If you want to use the latest version of SQL Compliance Manager, upgrade your deployment.
  2. Use Custom install in the SQL CM setup program to install the new Collection Server.
  3. If you upgraded SQL Compliance Manager to the latest version, also upgrade the compliance Agents deployed to the upgraded instances you are auditing.
  4. Configure the SQLcompliance Agent to communicate with the new Collection Server.

Deploy new Collection Server to audit new instances

  1. If you want to use the latest version of SQL Compliance Manager, upgrade your deployment.
  2. Use the Custom install in the SQL CM setup program to install the new Collection Server.
  3. Register the instances you want to audit.
  4. Begin auditing your new SQL Server instances.

 

SQL Compliance Manager audits all activity on your server. Learn more > >
  • No labels