Release Notes › System Requirements › Manager Requirements › Database Requirements

Database Requirements

CA Server Automation uses Microsoft SQL Server as its database. Because CA Server Automation integrates with other CA products, review the database requirements for integration products.

This release supports and is certified for the following versions:

• 2008 SP2 (32 bit, 64 bit), Standard and Enterprise Editions, SP3 optional
• 2008 R2 (32 bit, 64 bit), Standard and Enterprise Editions, SP1 optional
• 2008 R2 Express (32 bit, 64 bit), Database with Management Tools, and Database with Advanced Services Editions, SP1 optional
• 2012 (32 bit, 64 bit), Standard and Enterprise Editions
• 2012 Express (32 bit, 64 bit), Database with Management Tools, and Database with Advanced Services Editions

SQL Server Tools (OSQL.EXE) are required on the manager system to connect to a local or remote SQL Server database.

Important! If you are upgrading an existing 12.6 or 12.7 installation that uses SQL Server 2005: first upgrade the SQL Server to a supported version, verify that the 12.6 or 12.7 product is still operational, then upgrade to CA Server Automation Release 12.7.1.

Note the following considerations:

• For your convenience, SQL Server 2008 R2 Express Edition (32 bit) is available on the CA Server Automation installation media at the following location: DVD1\Installers\Windows\External\MSSQLExpress\setup.exe.
• Named instances and SQL Server clusters are supported. Enable TCP/IP and use static port assignments for each instance. Dynamic ports are not supported.
• The system that is installed with the manager components must also have the SQL client (server tools) installed.
• After the installation of SQL Server Tools, check to see that OSQL.EXE is properly installed to this location (if using the default install path):
  • MS SQL 2008: C:\Program Files\Microsoft SQL Server\100\Tools\Binn

Important! To ensure continued optimal performance, see the Microsoft KB Article 189858 for information on detecting and resolving database fragmentation.

Remote Databases

If you are using a remote database, the local system must have an appropriate matching version of the SQL Server Native Client.

Examples

• A remote 2008 SP2, R2, or R2 Express database requires a local 2008 SP2 or 2008 R2 Native Client, either is acceptable. A remote 2012 database requires a local 2012 Native Client.

The SQL Server Native Client is available from the Microsoft Download Center by searching, “Feature Pack for Microsoft SQL Server.” Based on your remote database and operating environment, complete these steps:

1. Select the most recent appropriate version.
2. Download and install the appropriate module for your operating environment on your local system.

   Example: ENU\<x86 or x64>\sqlncli.msi