Who is this article for?

IT Staff moving Ideagen Quality Management to a new server.

IT Permissions will be required to follow these steps.

The following article explains how to move your Ideagen Quality Management database to a new server.

1. Introduction
2. Moving the Database
3. Audit Log Database
   1. Moving the Audit Log Database
   2. Configuring Quality Management to use the Moved Audit Log
4. Updating the Application Server
5. Attachments

1. Introduction

Before you begin the database transfer you must:

• Ensure you have set up your new SQL server with mixed-mode authentication enabled.
• Confirm if you have the Audit Log feature enabled (you can confirm this in the Ideagen Quality Management Administration module under Licensed Features).

There are  3 stages to moving your database to a new server:

• Moving the Database
• Connecting the Audit Log
• Updating the Application Server

2. Moving the Database

1. Backup your existing live database.
2. On the new server, launch Microsoft SQL Management Studio.
3. Connect to your server.
4. Go to Object Explorer and expand Security, then Logins.
5. Right click on Logins and select New Login.
6. Name the account "QPulseAppUser".
7. Set this to use SQL Server authentication (and assign the same password as your existing server).
8. Uncheck Enforce password policy.

1. Click on the Status page at the left.
2. Grant the account access to login.
3. Click OK.
4. Restore the database backup taken in step 1 to your new/replacement server.
5. Run the following command against the database:

exec sp_change_users_login 'auto_fix','qpulseappuser'

3. Audit Log Database

3.1 Moving the Audit Log Database

If you have purchased the Audit Log add-on, you will need to ensure that the QPulseAuditLog database is moved to the new server as well as the QPulse database.

1. Backup your existing Audit Log database.
2. On the new server, launch Microsoft SQL Management Studio.
3. Connect to your server.
4. Go to Object Explorer and expand Security, then Logins.
5. Right click on Logins and select New Login.
6. Name this account "QPulseAuditLogUser".
7. Set this to use SQL Server authentication (and assign the same password as your existing server).
8. Uncheck Enforce password policy.
9. Click on the Status page at the left.
10. Grant the account access to login.
11. Click OK.
12. Restore your QPulseAuditLog database from the backup.
13. Run the following command against the database:

   exec sp_change_users_login 'auto_fix','qpulseauditloguser'

3.2 Configuring Quality Management to use the Moved Audit Log

1. Download the Audit Log connection script from Attachments.
2. Open this script in Microsoft SQL Management Studio.
3. Update the script by making the following changes:
   • Replace SERVERIP\INSTANCE with the IP address and the instance name of your SQL server.
   • Replace PASSWORD with the password set for your QPulseAuditLogUser.
4. Run the script against the QPulse database (not the QPulseAuditLog database).

4. Updating the Application Server

The application server will need to be updated before Ideagen Quality Management will use the database.

1. On the application server, go to the Ideagen Quality Management Server folder.  By default, this is:
   • 32-bit Windows: C:\Program Files\Gael Ltd\Q-Pulse Server.
   • 64-bit Windows: C:\Program Files (x86)\Gael Ltd\Q-Pulse Server.
2. Locate your DBConnections.xml file and open this with Notepad.
3. Edit the highlighted section below to include the IP address of your new server and the correct database instance name:

4. Double-check that the password specific matches the one set.
5. Save this file.
6. Launch ServerConfigUtil.exe.
7. Import the DBConnections.xml.
8. Click OK and save when prompted.
9. Re-start the QPulse Server service.

Note: When moving server the schema version of the database must match the version of the server. If an upgrade and a server move are being performed at the same time the database schema must be updated, as per the upgrade guide located in the Documentation folder of the version you are upgrading to.

5. Attachments