Testing Upgrades

In order to support new features, upgrades to the IssueView database schema are often required with new versions.  Under normal circumstances the database upgrade occurs while running the Setup for the newer version.  But IssueView is designed to allow database upgrades without running the Setup.  This allows you to manage and test multiple databases.

While it shouldn't be necessary to test the upgrade process (we do that during our regression testing of the product), sometimes it's nice to see how an upgrade will affect your particular situation.

Database upgrades are performed by the IssueView client software.  When the Setup is run, it checks for an existing IssueView database.  If an upgrade to the existing database is required, the Setup launches the new IssueView client to silently perform the database upgrade.

You can manually upgrade an older database with a newer client by logging into that database with the 'admin' UserID.  When you log in as Admin, IssueView checks to see if a database upgrade is necessary, and if so, prompts you to perform one.

You can test the upgrade process by making a backup copy of your database, then upgrading the backup.  This allows you to use the new features with your data, without any chance of causign problems in your production environment.  Once you're satisfied with the upgrade, you can discard the upgraded backup, and perform an upgrade in your production environment.

The process is slightly different for Access and SQL Server databases.

Testing an Upgrade to a SQL Server Database

These instructions assume that you're using a Test Machine that does not have SQL Server on it.

1. Download the latest IssueView 'Full' installation package which includes MSDE.

2. Install IssueView, and MSDE, on your Test Machine.

3. Launch the IssueView Desktop client and log in as admin.

4. Select 'Backup' from the Tools menu.  Name the backup copy of the database 'Test.bak' and press OK.  The file Test.bak will be created on the SQL Server.  You'll need to copy it to your Test Machine.

5. On the Test Machine, download RestoreBackup.exe.  If it complains about 'class not found', download and install the MSJVM.

6. Run RestoreBackup and restore Test.bak to your Test machine.

   Now launch the new IssueView client and log onto the database on the Test Machine.  This will be the same connection that was originally created on the machine, but it will now connect to the restored backup from your production server.

7. Log in as 'Admin' with the new version of IssueView.  You'll be prompted to upgrade the database.

Testing an Upgrade to an Access Database

1. Install the latest Client in a separate directory.  You don't need to install the database, as you're going to work with a backup of your existing one.

2. Launch the new IssueView client and connect to your existing older database.

3. Select 'Backup' from the Tools menu.  Name the backup copy of the database 'UpgradeTest.mdb' and press OK.

4. Now you need to create a connection to the backup database. Select 'Preferences' from the Tools menu.

5. Click on the Databases tab.

6. Click 'New' to create a new database connection, and enter the location information for UpgradeTest.mdb.  Name the Connection 'Upgrade Test'

7. Click OK until you're back at the main window, then select 'Log In As...' from the file menu.

8. In the login dialog, enter 'admin' for the User ID (the initial password was blank).  Be sure to select the 'Upgrade Test' database connection you created in step 6.

9. When you click OK to login, you'll be a message asking you if you want to upgrade your database.