Home > Support > Upgrades > Installing Upgrades

Installing Upgrades

Upgrade Steps

To upgrade QuantumCMS to the most recent version, we will go through five steps:

1. Prepare for upgrade and recovery
2. Upgrade SQL database
3. Upgrade Shared Authoring
4. Upgrade Public Site
5. Test

Preparing to Upgrade

Updates should only be applied to the Core QuantumCMS database, not to your application database(s). When upgrading, make sure you are only working against your QuantumCMS database.

1. Notify users of the upgrade and halt all authoring on the site. During the upgrade, the public site should stay functional but the authoring tool will be unavailable.
2. Back-up your QuantumCMS Database. You will use this to restore in the event of a failure during the upgrade.
3. Back-up the /Bin folder from your public site. In the event of a failure in the upgrade, copy the contents of the archived /Bin folder back into the public site's /Bin folder.

Updating the SQL Server

Executing the Core Service Pack

In the \Install folder of your deployment package, you will find a SQL Server script to upgrade your QuantumCMS Database. This will be called "QuantumCMS Version [Version Number] ServicePack.sql" OR "QuantumCMS Version [Version Number] ServicePack through HF[Hot Fix Number].sql".

e.g.
QuantumCMS Version 3.1.2 ServicePack through HF0007.sql

Execute this stored procedure against your QuantumCMS Database.

Executing Hot Fixes

Between full deployments, there may be hot fixes to your QuantumCMS database. If there are, you will find a Hot Fixes folder in your deployment package. If this folder does not exist, there are no new Hot Fixes.

Once the Core Service Pack has been installed, Execute any hot fix stored procedures in the order of their Hot Fix Number.

A note about errors when running upgrade scripts:

In executing the SQL Scripts, you may occasionally see an error indicating that an object could not be dropped because it did not exist, or that an entry in sysdepends could not be made. These errors may be ignored.

As part of every upgrade, any stored procedures that changed are dropped and recreated. If the stored procedure did not exist before, it will throw the first error. Also, some of the stored procedures used in QuantumCMS are recursive. These stored procedures can not find references to themselves in sysdepends and report the second warning.

Importing Core Quantum Form Data

Sometimes, updates require that the core Form and Form Control Tables in QuantumCMS be updated. You will find a batch file called "Import.bat" in the /Install folder of your deployment package. Beneath that folder, there will be a folder called SQLDAT.

This contains the table data to replace your core QuantumCMS tables. Your pages and data you have edited will not be impacted by this update. When the initial service pack was run, these tables were truncated.

In order to execute this part of the upgrade a program called BCP is required. This is a part of SQL Server so you must run the batch file from a machine that has either SQL Server or the SQL Server Client tools installed on it. It does not have to be run from the SQL Server you are updating.

To run the batch file, open a command window using Start \ Run. Navigate to the folder the batch file is located in. This folder must have the SQLDAT folder beneath it.

Execute the batch file supplying a username and password for SQL server, the server you want to connect to and the name of the Core QuantumCMS database you are upgrading. The syntax is:

Import.bat "[username]" "[password]" "[Server]" [Database Name]

e.g.
Import.bat "sa" "mypassword" "(local)" ABCCo_QCMS

You will notice that all of the arguments have double quotes except for the last one. Please maintain this format. Placing double quotes around the last argument will cause the upgrade to fail.

Once the batch file begins running you should see each table being updated and a count of the records copied in the command window. Check for errors. If all the tables failed because of an error in the arguments supplied, you may safely run the batch file again with the correct arguments.

If some of the updates succeeded and others failed, abort the upgrade and contact Algonquin Studios support. Please have the errors you received when running the import ready.

Importing Hot Fix Form Data

On very rare occasions, a hot fix may contain an update to the form and form control tables. If it does, apply the same procedures used in updating the Core Quantum Form Data.

Updating the Shared Authoring

Locate you current QuantumCMS Shared folder on your web server. When you receive a new version of the shared authoring tool, you should copy the \Shared Authoring v[Version Number] folder from your deployment folder into the root of the Quantum shared folder as a peer to other versions of the authoring tool.

The shared authoring tool will have two folders: Authoring and Bin.

Open Internet Information Server and navigate to your site's Authoring virtual directory. Change the path that is set for the virtual directory to be the "/Authoring" folder underneath your new Shared authoring folder.

Updating the Public Site

To update the public site, simply copy the contents of the new Shared Authoring v[Version Number]\Bin folder to the \Bin folder of your site.

Testing

Test that the public site and authoring work successfully. Be sure to check any custom applications you have developed. Although it is the policy of Algonquin Studios to not remove or modify any of the existing component interfaces for integrating with QuantumCMS, it is always best to be sure your applications function properly.