Upgrading v2.1 to v2.5

The version 2.5 of Visual Guard console needs to migrate the repository created by an older version of Visual Guard. This migration will alter the database structure of the repository. If you do not migrate these repositories, the Visual Guard console will not be able to access to them.

After migrating a repository, all applications using a Visual Guard runtime older than the version 2.1.701.10 will not able to access to this repository. For these applications, you must replace all referenced Visual Guard assemblies by assemblies more recent than the version 2.1.701.10.

Before migrating a repository, we strongly recommend to backup the data and the database structure.

It is possible to use the Visual Guard console to migrate the repository or execute SQL scripts installed with the product against the database.

Migrating the repository by using the Visual Guard console

Before migrating the repository, you must check that:

The Visual Guard user used to connect you to the repository is a 'Master Administrator'. If the user is not a 'Master Administrator', the console will not allow you to migrate the repository.
The underlying database user used to connect the console to the database has enough rights to alter the database structure of the repository (Tables, Roles, Stored Procedures). If an error occurs during the process, the repository can be damaged.

To migrate your repository, you must declare the repository in the list of repository (if needed) and connect you to the repository by using a 'Master Administrator' user. During the connection, the console will automatically detect that the repository needs to be migrate and will ask you a confirmation before launching the migration process.

Migrating the repository by using the SQL Scripts

If you or your DBA want to migrate manually your repository, you can use SQL Scripts installed with the product. These scripts need to be modified before running against the database.

For Oracle database migration: you can find the script 'Upgrade2_1_701_10to2_5_705_30.SQL' in the directory '<Visual Guard installation directory>\VisualGuardConsole\Database\Oracle'. You must modified the script to change the value <VISUAL_GUARD_SCHEMA> by the schema name containing Visual Guard tables.

For SQLServer database Installation: you can find the script 'Upgrade2_1_701_10to2_5_705_30.SQL' in the directory '<Visual Guard installation directory>\VisualGuardConsole\Database\SQLServer'. You must modified the script to change the name of the database (by default 'visualguarddb') by the database containing Visual Guard tables.