Skip to Content

When you install Crystal Reports Server, you have the option of either selecting a database to use for the System Database (or repository) or the setup program can install and configure MySQL for you.

 

Many installations will start of using MySQL and then look to move their system database to another database server, like SQL Server, Oracle, DB2, etc.

 

To move your system database from MySQL to another database (in this case, SQL Server), select a time when there will be no users who need to access the server and then follow these steps:

1. Backup      your existing MySQL database. There is a great article on how to backup a      database using the MySQL utility mysqldump, which is available from:

   

http://www.devshed.com/c/a/MySQL/Backing-up-and-restoring-your-MySQL-Database/

2. Check      the Supported Platforms document to make sure your version/service pack of      SQL Server is supported.

3. On      the SQL Server, create a blank database

4. On      the server where you installed Crystal Reports Server, create an ODBC      system dsn that points to the blank database you have created.

5. Next,      go to the server and select Start > Programs > Crystal Reports Server      2008 > Crystal Reports Server 2008 > Central Configuration Manager      as shown below in Figure 1.

 

 

6. To      change the system database, you will need to stop the SIA service, which      in turn will stop all of the other BusinessObjects services. Highlight the      SIA service, shown below in Figure 2 and then click the Stop button in the      toolbar.

 

 

7. Next,      right-click on the SIA service and select Properties and navigate to the Configuration      tab.

8. Locate      the CMS System Database Configuration area and click the Specify button,      as shown below in Figure 3.

   

 

9. A      dialog will appear presenting three options for specifying the system      database. Since we are moving the system database, select the first      option, which is “Update Data Source Setting” as shown in Figure 4

 

 

10. Once      you have selected this option and clicked OK, you will be presented with a      list of available data sources, as shown in Figure 5.

 

 

11. Select      the option for SQL Server (ODBC) and then select the ODBC System DSN that      you created earlier using the dialog shown below in Figure 6, then  click OK.

 

 

   

You may be asked to login—make sure you login with a SQL Server account that has the rights to create tables, etc. (If in doubt, get your DBA to login to do this step.)

Once the database transfer is complete, you can then restart the SIA service—the easiest way to check that the transfer was successful is to login to InfoView (http://servername:8080/InfoViewApp) or the Central Management Console (http://servername:8080/CmcApp) and navigate around, schedule a few reports, etc.

If the SIA service itself won’t start, check out the Windows Event Viewer to check for any error or warning messages that may appear.

This technique can also be applied to SAP BusinessObjects Edge and SAP BusinessObjects Enterprise. It also can be used to move the system databases to other database formats. In the case of DB2, Oracle, etc. you don’t need to create an ODBC connection to the database, as you can correct to these database platforms natively.

 

 

 

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Peter Vermeulen
    In step 9, I would expect to select the “copy” option to move all the data from MySQL into the new MSSQL. Otherwise the MSSQL would still be empty no?
    (0) 

Leave a Reply