upgradetest
Use the upgradetest program to check for potential problems with updating the database. It runs all the necessary patchdb scripts to make sure there are no surprises from the database side.
This program is shipped along with the installation package.
Requirements
Before running this tool, you must copy the production database to another server.
The server to which the database is copied must be the same edition as the production database. The result of the db script executions by upgradetest will differ depending on the edition of SQL Server it is running against. If that edition differs from production, it may result in false positive errors or otherwise inaccurate results.
The upgradetest utility must be run from the installation folder where it is provided. It relies on idm.msi (or idm-debug.msi) to be in the same folder. It will then know which upgrade scripts to run from that .msi file.
Best practice
Use the utility from the installation package for the version to which the instance will be upgraded.
Preparation
Before running upgradetest:
Copy the instance database to another SQL server.
Set up an account that has access to the database copy.
The account should be similar to the production account that Bravura Security Fabric uses to access the database (name can differ, but permissions and access should be the same). See Database, user, schema for steps to set up the user.
Copy the installation package to the new server.
Usage
upgradetest.exe -db <database> -s <server> [ -u <user> ] [ -windowsauth ]
Argument | Description |
|---|---|
-db, --db <database> | Name of the database to upgrade (required) |
-s, --server <server> | Address of SQL Server backend (required) |
-u, --username <username> | User name to connect to SQL Server backend with |
-windowsauth | Use Windows authentication using the current user (do not prompt for password) |
Example
upgradetest.exe -s sqlserver -db enterprisedb -u sqladmin