Steps for manually upgrading Blueprint Analyst databases from 3.5 to 3.5 SP1
============================================================================
The following instructions explain how to manually upgrade the Blueprint Analyst databases.

 

A manual upgrade of the Blueprint Analyst databases will be required if the original install was to a remote database, with the databases hosted on SQL Server running on a separate machine from the other Blueprint components. The remote database will typically have been installed manually when Blueprint was originally installed.

 

These instructions apply to the manual upgrade of the Blueprint Analyst databases from 3.5 to 3.5 SP1
All the files required to carry out a manual upgrade of the databases are available in the 3.5 SP1 under ".\Program Files\PharosSystems\Blueprint\Database\MSSQL"

 

Preparation
-----------
1. In the Services Control Manager, stop the Pharos Systems TaskMaster and Pharos Systems TaskMaster Watchdog services.
2. Close all copies of the Blueprint Administrator connected to the Blueprint Analyst databases.
3. Backup the Blueprint Analyst databases, by executing the "Pharos Blueprint Database Backup" SQL Server Agent job through SQL Server Management Studio. Copy the resulting backup files to a secure location.

 

Database Upgrade
----------------
1. Upgrade psbprocs database.
This step detaches and then re-attaches a new copy of the psbprocs database and will require either the "sa" or a Windows Administrator account

 

Using SQL Management Studio open and execute contents of the file .\Common\UpgradeDetachProcsDB.sql against the master database. This detaches the existing psbprocs database from the SQL Server.

 

Copy the new psbprocs.mdf and psbprocs.ldf files from CD to the server.
The files should be copied from the CD from either .\Analyst\SQL2000 or .\Analyst\SQL2005, depending on the SQL Server version and should be copied to the same location as the old psbprocs database files, first copying the old files to the same secure location as the database backup files.

 

The Database files are located under the following directory in BluePrint 3.5
C:\Program Files\PharosSystems\Blueprint\Data

 

Using SQL Management Studio open the file .\Common\UpgradeAttachProcsDB.sql and connect to the master database.
Edit this file replacing the parameter placeholders with the Blueprint SQL logon and the location of the psbprocs database files.
For example
    set @Logon                            = N'||SQLLogonName||'
    set @MainDataFileFolder    = N'||MainDatabaseDataFileFolder||'
    set @MainLogFileFolder      = N'||MainDatabaseLogFileFolder||'

 

would updated as follows, if the SQL logon was "psbprint" and the file location was  "C:\Program Files\PharosSystems\Blueprint\Data "
    set @Logon                           = N'psbprint'
    set @MainDataFileFolder   = N' C:\Program Files\PharosSystems\Blueprint\Data’
    set @MainLogFileFolder     = N' C:\Program Files\PharosSystems\Blueprint\Data'

 

Execute this script to attach the new psbprocs database.

 

2. Upgrade the partition databases psjobs[1..N]
This step updates the schema in each of the psjobs databases and can be carried out using the Blueprint SQL logon account, the "sa" or a Windows Administrator account.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradePartitionHead.sql against the psjobs1 database.

 

Depending on the volume of data in the database this script may take a few minutes to run.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradePartitionTail.sql against the psjobs1 database.

 

Repeat the above steps for each of the partition databases psjobs[1..N].

 


3. Upgrade the main psbprint database
This step updates the schema in the main psbprint database and can be carried out using the Blueprint SQL logon account, the "sa" or a Windows Administrator account.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradeAnalystHead.sql against the psbprint database.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradeAnalyst4685.sql against the psbprint database.

 

Depending on the volume of data in the database this script may take a few minutes to run.

 

Using SQL Management Studio open and execute contents of the file .\Analyst\UpgradeAnalystTail.sql against the psbprint database.
This completes the manual upgrade of the database.

 


The Blueprint Analyst components can now be upgraded using the 3.5 SP1 Installers.
The Pharos Systems TaskMaster service will not restart cleanly until it has been upgraded.

 

To check if the database has been upgraded successfully run the following query:
select * from databaseversion against psbprint it should return 4685 as the BuildNumber.