Knowledge base

Upgrading to a later version of SQL Monitor

Upgrading to a later version of SQL Monitor will preserve all your current monitoring data in the Data Repository. SQL Monitor will automatically modify the schema of the Data Repository database to the newer version during the installation process.

How do I know when an upgrade is available?

SQL Monitor will display a message above the product name banner when a later version is available:

Click on the link for more information about the newer version, and a link to download it.

Before upgrading

Before you upgrade to a later version, we recommend that you back up your current Data Repository. Once the upgrade is completed, you will not be able to roll back to a previous version of your Data Repository database; we therefore recommend you make a backup of this database before installation.

Upgrading from v2.x to v3.x

You should only upgrade to v3.x if your current SQL Monitor license includes a valid support and upgrades package.

If you upgrade with a support and upgrades package, the v2.x activated licenses will expire and SQL Monitor will reactivate them as v3.x licenses.

If reactivation fails, or your v2.x license does not include support and upgrades, SQL Monitor will delete the serial numbers from the Configuration > Licensing page and start a 14-day trial version of v3.x. You cannot roll back to the previous 2.x version, so we recommend that v2.x users without a valid support and upgrades package install a trial version of v3.x on a separate machine. When v2.x users are ready to purchase v3.x licenses, they can add the support and upgrades package to make upgrading easier.

• To find your v2.x serial numbers, go http://www.red-gate.com/myserialnumbers to and enter your email address and password.
• To find out whether your license includes a valid support and upgrade package, go to http://www.red-gate.com/upgrade and enter your serial number.
• To purchase a v3.x license with the support and upgrades package, contact dba.info@red-gate.com.

Upgrading from v2.0 to v2.1 or higher

If you are upgrading from v2.0 to versions 2.1 or above, you will need to uninstall the 2.0 Base Monitor and SQL Monitor Web Server components before you can install the newer version. Use Add or remove programs to uninstall SQL Monitor Base 2 and SQL Monitor Web 2. (If you are using an IIS server, this second component should not be installed).

If you are upgrading from v2.1 or later, you do not need to uninstall any SQL Monitor components.

Installing the new version

1. Run the installer, and follow the wizard to install the Web Server and Base Monitor.
2. On the Set up Data Repository page, supply credentials with db_owner permissions under Connect to Data Repository database using:

   

   SQL Monitor will use these credentials to upgrade the Data Repository at the end of the installation process.

3. Click Next. The installer will prompt you to take a backup of the Data Repository before continuing:

   

4. When you have successfully backed up the Data Repository database, complete the rest of the wizard and click Install. All the components are installed. SQL Monitor will attempt to upgrade the database schema as soon as the web service is running successfully.
5. If you open SQL Monitor in your browser before the upgrade is complete, you will see the schema upgrade progress bar:

   

   If the upgrade is successful, your browser will then display the Enter password page or the Global Overview.

   If the upgrade is not successful, an error page is displayed.

Error when upgrading?

If you encounter an error page when upgrading, please refer to the error message highlighted in the box. All error messages are those returned by SQL Server and not SQL Monitor.

The most common reason why the Data Repository cannot be upgraded is that the supplied account lacks the sufficient permissions to modify the database. Enter an account with db_owner permissions and click Retry Upgrade.

Note: This account is used only to upgrade the database schema. It is not required by SQL Monitor for anything else.