Migrating SQL Server database schemas for CR2

Run SQL scripts to update IBM® Connections 5.5 or 5.5 CR1 database schemas to CR2 in an existing IBM WebSphere® Application Server and Microsoft™ SQL Server database environment.

Before you begin

Before applying updates, back up your databases. For more information, see Backing up IBM Connections.

Ensure that you have installed and configured all supporting software for version 5.5.

About this task

This topic describes how to update IBM Connections 5.5 databases to CR2.

Notes:

After you run each command, examine the output of the command for error messages. If you find errors, resolve them before continuing with the update process.
To improve readability, some commands and file paths in this topic are displayed on separate lines. Ignore these formatting conventions when you enter the commands.

To update databases manually, complete the following steps:

Procedure

From the 5.5 package, copy the 55cr2-database-updates.zip file to a temporary directory on your database server.
Extract the SQL scripts pertinent to your version and database platform, preserving the folder structure.
Log in to the WebSphere Application Server Integrated Solutions Console on your Deployment Manager.
Go to Applications > Application types > WebSphere enterprise Applications.
Stop all IBM Connections applications.
Log in as the database administrator.
Change to the folder where the SQL scripts were extracted for your version of Connections and the database product you are using.
If you preserved the folder structure of the .zip file, the SQL scripts are organized by version number.
- Scripts for updating 5.5 databases are in the 55cr2-database-updates\From-55 folder.
Skip this step if you are updating databases from 5.5 CR1 to CR2.
If you are updating databases from 5.5, navigate to the sql folder from the 55cr2-database-updates\From-55 folder.

For each application, run the appropriate scripts by entering the commands that are shown in the following list. In these commands, dbPassword is the password for the SQL Server user named sa. If your database server has multiple SQL Server instances that are installed, add the following text as the first parameter to each command:

-S sqlserver_server_name\sqlserver_server_instance_name
where
- sqlserver_server_name is the name of your SQL Server database server
- sqlserver_server_instance_name is the name of your current instance
Note: To capture the output of each command to a log file, append the following parameter to each command:
>> \file_path\db_application.log

where file_path is the full path to the log file and application is the name of the log file.
For example:
sqlcmd >> \home\admin_user\lc_logs\db_activities.log
where sqlcmd is a command with parameters and admin_user is the logged-in user. Ensure that you have write permissions for the directories and log files.
1. Enter the following commands one at a time to update the Homepage, Activities, Files, Mobile, and Wikis databases to 5.5 CR2:
```
-i 55-CR1-homepage-sqlserver.sql
-i 55-CR2-activities-sqlserver.sql
-i 55-CR2-files-sqlserver.sql
-i 55-CR2-homepage-sqlserver.sql
-i 55-CR2-mobile-sqlserver.sql
-i 55-CR2-wikis-sqlserver.sql
```
Skip this step and go to What to do next if you updated your databases from 5.5 in the previous step.
If you are updating databases from 5.5 CR1, navigate to the sql folder from the 55cr2-database-updates\From-55 CR1 folder.

For each application, run the appropriate scripts by entering the commands that are shown in the following list. In these commands, dbPassword is the password for the SQL Server user named sa. If your database server has multiple SQL Server instances that are installed, add the following text as the first parameter to each command:

-S sqlserver_server_name\sqlserver_server_instance_name
where
- sqlserver_server_name is the name of your SQL Server database server
- sqlserver_server_instance_name is the name of your current instance
Note: To capture the output of each command to a log file, append the following parameter to each command:
>> \file_path\db_application.log

where file_path is the full path to the log file and application is the name of the log file.
For example:
sqlcmd >> \home\admin_user\lc_logs\db_activities.log
where sqlcmd is a command with parameters and admin_user is the logged-in user. Ensure that you have write permissions for the directories and log files.

Use these scripts to update the Activities, Files, Homepage, Mobile, and Wikis databases to 5.5 CR2:
```
-i 55-CR2-activities-sqlserver.sql
-i 55-CR2-files-sqlserver.sql
-i 55-CR2-homepage-sqlserver.sql
-i 55-CR2-mobile-sqlserver.sql
-i 55-CR2-wikis-sqlserver.sql
```

What to do next

Check that all the databases are working correctly.