Knowledge Base >> Moving SQL Server Data Warehouse Repositories

Moving SQL Server Data Warehouse Repositories - Confio Article 1532

Confio Article: 1532 Published: Jan 05 2009 10:00 AM
Version: Topic(s): Database Problems Ignite Management
Product(s): Ignite
Database(s): MS SQL

Overview

Confio Ignite™ PI can utilize SQL Server 2000, 2005 or 2008 for the Performance Data Warehouse (Repository). This application note provides instructions for moving an Ignite PI data warehouse repository from one SQL Server instance to another.

 

Instructions

This document assumes that the target SQL Server instance is already created.  Remote Connections must be enabled to allow TCP/IP and/or Named Pipe connections.

 

1. Stop All Monitors on the current SQL Server Repository.

Step 1

 

2. Shutdown the ‘Ignite PI Server’ service on the server.

 

3. In SQL Server Enterprise Manager, take a backup of the Repository database.  Highlight Ignite’s repository database and right-click for ‘All Tasks’ > ‘Backup Database’.

Step 3

 

4. Fill out the backup page with the database name and select the ‘Database – Complete’ option.  Add a location and file name for the backup.

Step 4

 

5. Copy the backup file to the machine where the target SQL Server instance resides.

 

6. In SQL Server Management Studio on the target instance, highlight the Databases menu and right-click to choose the ‘Restore Database’ option. Enter the name of the database just backed up in the ‘To Database’ field. Choose the ‘From device’ option and add the location and filename of the backup file.  Check the ‘Restore’ box  and select ‘OK’

Step 6

 

7. Create Ignite Internal user by choosing Security > Logins > Right-Click > New Login,

Step 7

 

8. Choose the Server Roles menu and give the new Ignite User the same security privileges as the old Ignite User.

 

9. On the ‘User Mapping’ menu, map the Repository Database to the Ignite user. Give the new Ignite user the same Database roles as the old Ignite user had in the old repository.

 

10. Test connectivity by remotely connecting to the Repository Connection User from SQL Server Management Studio.

 

11. Edit Ignite’s repo.properties file and change the connection information. The file is located in Ignite’s install directory – default location is:

C:\Program Files\Confio\Ignite PI\iwc\tomcat\ignite_config\idc

Example of repo.properties contents – change the bolded information to the new Server\\Instance information. 

repo.serviceName=
repo.port=1433
repo.user=ignite_jg2k
repo.databaseType=SQL Server
repo.guid=6cafc93f8e5ab80d\:18020cc\:11bb7796832\:-7ffb
repo.created=yes
repo.databaseName=ignite_ignite_jg2k
repo.host=SEBOX1\\SE12005
repo.password=4F9717C431843DC8C29448
repo.name=IGNITE_JG2K@SEBOX1\\SE12005

Note: If you’ve kept the same port, database name, repository connection user and password information, you will not need to edit these fields.

12. Startup the ‘Ignite PI Server’

13. Ensure that all Monitors start up in Ingite.

 

Troubleshooting

To report issues to Confio Support, zip up the ‘logs’ directory usually located in C:\Program Files\Confio\Ignite PI\iwc\tomcat\ directory and send to support@confio.com.  To research connectivity issues to the new server, review the idc.log and idc-errors.log files for further information.

Tags: data pi SQL ignite move moving server warehouse transfer migration repositories