SQL Server Database Setup

If you use Microsoft SQL Server, you must set up a SQL Server database for each workspace repository you plan to create. If CA users connect to the repository through an SQL Server login account, ensure the server authentication property is set to SQL Server and Windows Authentication mode, as described below.

The following instructions assume you are using the SQL Server Management Studio tool for SQL Server 2008. The procedure for the SQL Server Management Studio Express tool for SQL Server 2005 is similar.

Note: For Windows XP installations using the Italian locale, you must set the Time format in the Control Panel Regional Language Options to "HH:mm:ss" before attempting to verify an CA workspace with a SQL Server repository. Click Settings > Control Panel > Regional and Language Options > Customize > Time and choose "HH:mm:ss" from the Time format list.
  1. Click Start > Programs > Microsoft SQL Server 2008 > SQL Server Management Studio.
  2. In the Connect to Server screen, select:
    • Database engine in the Server type list.
    • The server on which you want to create the repository database in the Server name list.
    • Windows Authentication in the Authentication list.
  3. Click Connect. The Microsoft SQL Server Management Studio window opens. In the Object Explorer pane, expand the folder for the server. Click Databases and choose New Database from the right-click menu. The New Database window opens.
  4. Select the General page. In the Database name field, enter the name of the database for the repository. Modify the logical name and initial sizes of the database and log files if needed, then click OK. The new database is displayed in the Object Explorer pane.
    Note: The database collation should be case insensitive. Additionally, check the SQL Server Management Studio documentation for details on other database settings.
  5. If you connect to the workspace repository through a Windows user account, skip the remaining steps. If you connect to the workspace repository through an SQL Server login account, click the server name in the Object Explorer pane and choose Properties from the right-click menu. The Server Properties window opens.
  6. Select the Security page. In the Server authentication area, select SQL Server and Windows Authentication mode, then click OK.
  7. In the Object Explorer pane, click Security > Logins and choose New Login from the right-click menu. The Login - New window opens.
  8. Select the General page. In the Login name field, enter the database login name, then choose SQL Server authentication. Enter the password for the database login in the Password and Confirm password fields, then click OK. The new login is displayed in the Object Explorer pane.
  9. In the Object Explorer pane, expand the database you created for the workspace repository. Click Security > Users and choose New User from the right-click menu. The Database User - New window opens.
  10. Select the General page. Define the database user:
    • In the User name field, type the database user name.
    • In the Login name field, type the database login name. Use the Browse button to browse for the login name.
      Note: You specify the login name, not the database user name, when you create or connect to a workspace, so it is usually best to make the user name and login name the same.
    • In the Database role membership pane, check db_owner, then click OK. The new user is displayed in the Object Explorer pane.
    Tip: You can use the same login and database user for multiple databases or workspaces.

You can configure COBOL Analyzer to build a workspace on one machine for a single user. You can use Microsoft SQL Server Express - installed by default - to create a workspace on your local machine. CA creates a database for the workspace "on the fly," with no intervention on your part. If you do use SQL Server Express, bear in mind that the Windows user who creates the workspace must have been configured with appropriate permissions in SQL Server Express. The user who installed SQL Server Express will always have the appropriate permissions. See the SQL Server Express documentation for configuration instructions.

Restriction: The database size limit when using the SQL Server Express option is 10 GB.
Note: SQL Server database transaction logs can become full, resulting in errors. To avoid this, Micro Focus recommends that you turn off transaction logging or implement automatic log recycling so that normal CA processing is not interrupted. CA does not use the SQL recovery processes so the transaction logging is not required, but it is recommended that the database is regularly backed up.

collation