Installation of CA ITCM › Management Database (MDB) › Preparing to Work with a Microsoft SQL Server MDB

Preparing to Work with a Microsoft SQL Server MDB

Before you install a DSM manager based on Microsoft SQL Server, the SQL Server must have been installed with the following configuration:

• Mixed mode authentication (that is, Windows authentication and SQL Server authentication) is required
• TCP/IP network protocol is enabled and operational. For information on how to choose and configure network protocols, see the SQL Server documentation.
• The following rule applies to the server collation selected during SQL Server installation:

  You must choose a collation name where a case insensitive variant is supported.

Use the CA ITCM installation wizard and follow the instructions to configure the SQL Server MDB, as follows:

• On the "Configure Manager" page of the wizard, you must enter the mandatory specifications (connection parameters) for the target database system, such as:
  • Management Database Provider (select Microsoft SQL Server)
  • Management Database Server
  • MDB Password

    Note: Because mixed mode authentication is used, this password must conform to the security level of a system login password.

• On the "Configure Microsoft SQL Server MDB" page you can enter the following configuration settings:
  • Compatibility mode

    Note: The Compatibility mode check box must be selected if you are going to install a new MDB 1.5 as shipped with the product and you have planned to later install another CA Technologies product that only supports MDB 1.0.4. If the Compatibility mode check box is not selected, the installation of any follow-up product that does not support MDB 1.5 will fail.

    Default: Compatibility mode is not selected.

  • MDB database name

    Default: mdb

  • MDB instance name.

    Select the instance name from the drop-down list.

    Default: default

  • Database port number

    Default: 1433

During installation, you must enter the port number associated with the Microsoft SQL Server instance for all nondefault instances. The port can be looked up in the SQL Server TCP/IP configuration using SQL Server Configuration Management.

If Microsoft SQL Server is being configured with named instances, the "TCP Dynamic Ports" option is automatically set with the port number (dynamic port configuration). Then, it may happen that the domain or enterprise manager cannot access the database because the port number on the MDB system has changed in the meantime, for example, due to a system restart. To avoid these access failures, we recommend that you change the port setting manually to a static port ID, as follows:

• From the Windows Start menu, open SQL Server Configuration Manager, SQL Server Network Configuration, Protocols for instance_name, TCP/IP.
• Right-click and select Properties from the context menu.
• On the TCP/IP Properties dialog select the IP Addresses tab. In the IPAll area, cut the port value in the TCP Dynamic Ports field and paste it into the TCP Port field.

Important! In case you assign a nondefault port number manually, we recommend that you update the reservedPorts list in the registry. Otherwise, it could appear that CAF is started before SQL Server after a reboot; and then, if CAF requests a dynamic port number, it could be that CAF gets the port number that was set for the SQL Server. As a result, the SQL Server will fail upon startup.