Installing CA SRM › Using Microsoft SQL Server as the CA SRM Database › Microsoft SQL Server Database Considerations

Microsoft SQL Server Database Considerations

Review the following information for using Microsoft SQL Server to support the CA SRM database:

• CA SRM supports Microsoft SQL Server 2005 / 2008 / 2008 R2, and 2012.
• By default, CA SRM creates the following databases in addition to some temporary databases. Retain this model for proper operation.
  • <SRM_SERVER_NAME> ENTRPRIS
  • <SRM_SERVER_NAME> QUERIES
  • <SRM_SERVER_NAME> SAVED_USER_QUERIES
• Microsoft SQL Server supports local and remote communication. This capability lets you install the CA SRM database locally or remotely to your CA SRM Application server.
• Based on the number of objects that CA SRM manages, the database size is expected to grow at a faster rate. Based on your organization needs, plan to have enough free disk space to support the growth of CA SRM Database.

Prerequisite

To install SRM with Microsoft SQL Server, use one of the following accounts for successful installation:

• An SQL account such as 'sa'
• Any windows account that has administrative (sysadmin) access

Remote Database Considerations

Using a remote database provides a simple and transparent method of sharing a single database just like a local database. When you use this configuration, you do not need a database on the local machine because all information is saved to the remote database. This configuration is best under the following conditions:

• When there is not enough space locally for the database.
• When you want to take advantage of the ease of management that comes with having a single location for the database.
• When you require a separate server that is not a CA SRM server to function as a dedicated Microsoft SQL Server.
• When you require protecting SQL Server instances in a cluster-aware environment.

SQL Database Connections

CA SRM uses some SQL connections out of which some are fixed and rest are temporary connections. You need a minimum of 15 base connections on an Application Server, two for each Windows Client standalone, and one for each database update job.

Example

If you plan to have one Application Server, three Windows Clients, and plan to leave the maximum concurrent data collections at three, you would need Base (15) + 3x2 + 3 = 24 connections.