Upgrade BPC RiskManager Database Installation
Introduction
Four options are offered for upgrading the database. The easiest and safest is to either let the installer do it for you (option 1.) or get us to do it for you (option 3). Alternatively, with a small amount of skill and a little certainty as to which database version you are running, you can run the provided upgrade scripts. Upgrade scripts for the most commmon BPC RiskManager versions are provided in your installation folder. Note there are versions for SQL 2000 and SQL 2005 (and above) You must run each script for the appropriate server in the numbered order on EACH RM database. Script sets usually include structure and data update groups. You are also welcome to contact Bishop Phillips Consulting directly for any unusual scenarios.
OPTION 1:
The installer will do it for you. For every version after 6.18 the installer will allow you to nominate database(s) to be upgraded and the last RM application version to which each database applied and perform the database upgrade for you. This is by far the easiest option.
OPTION 2:
Database scripts are used to upgrade a risk database. Database scripts MUST BE RUN IN THE NUMBER ORDER PROVIDED IN THE SCRIPT DIRECTORY as each script applies the updates from one version to the next only. All database scripts can be run without the need for customisation (changes to the script files). If you do not want to run a standard order of installation please contact Bishop Phillips Consulting before modifying scripts.
To upgrade a risk database from a prior version please run the database upgrade scripts provided. Database upgrade scripts must be run in the correct order from lowest version number to the highest available. Each upgrade script will progressively upgrade the database structure to meet the requirements of each minor upgrade release of Risk Manager.
In some cases we will provide scripts to go directly from your database version to the target version.
In all cases a script's target database versions are identified in the name: eg "1_BPCRMUPDT_StructV618_to_625.sql" or something similar. The left hand number is the "from" database version, while the right hand number is the "to" database version. The version numbers are the database build version numbers and may nor exactly match the client version numbers.
How to determine what data structure version of Risk Manager you are running: Run database query:
"select sys_val from system_config where (module='RM') and (context='SYSTEM') and (keyname='DATA STRUCT VERSION');"
OPTION 3:
If you have any doubt about what you need to do to upgrade a database you can backup one of your databases, compress the backup into zip format and send it to Bishop Phillips Consulting (or arrange for us to download it from your server) and we will generate a custom update script, convert you database (and check you database for errors at the same time), and provide it back to you on a secure ID for download – all for a tiny nominal fee.
OPTION 4:
If you have a database comparator tool available such as SQLDelta and you know how to use it, you can install the new supplied default database on a server and run the database comparator between the old database and the new one. You should accept 100% of the structure changes. There may also be data changes in the new release, and these are best handled by running the "data update" sql script, or if you wish to use the comparator for that as well you should request a current list of tables for data comparison from BPC.
Option 4 requires a very powerful comparator tool (covering tables, views, procedures, triggers, indexes, user defined datatypes, constraints, and referential inegrity rules), and an advanced understanding of the comparator software, the riskmanager database, and SQL. It is NOT the recommended option and should be done in consultation with a BPC technical support officer. Remember to backup your database(s) first.
