Blueprint Enterprise: How to migrate the Analyst databases from one SQL Server to another

Goal:

Migrate the SQL Databases use by Blueprint Enterprise from one SQL Server to another SQL Server.

Environment:

Blueprint Enterprise 5.1
Blueprint Enterprise 5.2
Blueprint Enterprise 5.3

Steps:

See the attached PDF.
It may be necessary to move the Pharos Blueprint Enterprise databases from one Microsoft SQL Server to another. This document outlines the steps necessary to perform this task. Note that if you are distributing Pharos iMFP for Hewlett-Packard FutureSmart via HP’s Web JetAdmin application, changing the location of the Pharos Blueprint databases will also require modifying the HP Application Service’s “Fleet deployment” configuration (per server). 

PREPARATION 

Identifying the databases must first be done prior to the migration activity. In general, the following databases will require migration: 

• psbprint

• psjobs1 

• psjobs2 

• psjobs3 

• psjobs4 

• psreports 

• SiteMonitor 

Depending on the size of your site, there may be “psjobs” databases beyond psjobs4. 

MIGRATING THE DATABASES 

Once the databases are identified: 

1. Stop both the Pharos Systems Taskmaster and Pharos Systems Site Monitor services on the Blueprint Analyst server. 

2. Perform a “full” backup of each database, taking note of each backup file’s destination. 

3. Copy the backup files to the new SQL Server’s disk. 

4. Restore the backup files to a new database. 

5. Create a SQL login and provide it a password that meets organization requirements. 

6. Run the following T-SQL script, changing the database name for each database restored: 
    
   USE DatabaseName  --for example, USE psbprint 
   GO 
   EXEC sp_changedbowner 'login';  --specify the login from step 5 
   GO 

RECONFIGURING PHAROS BLUEPRINT 

1. Launch the Pharos Systems Blueprint Server Configuration tool on the Analyst, and select the Database tab. 

2. Enter the SQL server/instance for both the Operational and Reporting databases (use the drop-down menu for “Select the database to configure” option to toggle between the two), as well as the user credentials. See the sample image below: 

3. Ensure to test the connection and that a connection success message is returned. 

4. Click the Apply button to set the configuration and restart the Pharos Blueprint Analyst application. 

RECONFIGURING PHAROS SITE MONITOR 

1. On the Analyst server, navigate to the X:\Program Files (x86)\PharosSystems\SiteMonitor\Service folder, where X is the drive letter onto which Blueprint Enterprise was installed. If the Windows OS is 32-bit, navigate to the X:\Program Files\PharosSystems\SiteMonitor\Service folder. 

2. Move the PharosSystems.SiteMonitor.Service.exe.config file out of this folder and place it on the desktop temporarily. 

3. Launch the SiteMonitor.msi installer from the Blueprint installation package. 

4. Click the Next button. 

5. Choose the Repair option. 

6. Within the Site Monitor Setup window that appears, enter the correct SQL server instance, username and password for the SiteMonitor database. 

7. Click the Next button. 

8. Click the Repair button. 

9. Click the Finish button when completed. 

10. Launch the Pharos Systems Site Monitor Administrator to verify that the service is online and operational.