Upgrading or Updating Velocity
- Anand Rajaraman
- Del Gonzalez
If you have an existing Velocity installation, you can upgrade or update it instead of performing the new installation described in the Updating from v3.6 (or higher) to v3.8.6 section.
Upgrades versus Updates
In the past, moving an existing Velocity system to the next major release required an upgrade, which typically included some changes to the structure of the Velocity database. An upgrade was indicated by an increase in the major release number, from 3.5 to 3.6 or 3.7 to 3.8.x.
Starting with version 3.5, minor releases were called Service Packs. These updates could be applied more quickly to an existing system (within the same major release) using a Velocity Update Wizard (instead of the full Velocity Installer). An update was indicated by an increase in the minor release number, such as from 3.5 SP1 to 3.5 SP1.1 or from 3.6 SP2.1 to 3.6 SP3.
Starting with Velocity 3.6, you can now update to newer major releases (in addition to minor releases) of Velocity using the Velocity Update Wizard instead of the full Velocity Installer.
Moving from any Velocity 3.6 release (3.6 SP3) to a 3.7 release (3.7 SP1) is an update instead of an upgrade. To better understand this change, look at the following diagram, which shows the upgrade paths from earlier Velocity versions to the initial 3.7 release. Note that when moving from 3.6 to 3.7, you must use the Velocity Update Wizard instead of the Velocity Installer.
Existing Velocity users moving from 3.6 or 3.7 to 3.8.x use the Velocity Update Wizard. This wizard simplifies the effort required to upgrade and uses smaller installation files than the Upgrade Wizards provided for previous Velocity versions.
Upgrade Paths
There are specific upgrade paths you can choose from. In the following diagram, locate your existing version of Velocity, then follow the best available upgrade path to your latest Velocity:
Your upgrade path to the latest Velocity release depends on which older version of Velocity you are currently running. To summarize your options (as shown in the previous diagram):
If you are still running an older version of Velocity, which is not shown in the diagram, you must start by upgrading to the 3.1 KB640 release. Then you should upgrade to the 3.5 SP2.1 release, upgrade to the 3.6 SP3 release, then update to the 3.7 or 3.8 release.
If running any 3.5 release, you must upgrade to the 3.6 SP3 release and then update to the 3.7 or 3.8 release.
Microsoft no longer supports Windows XP, and Velocity 3.6 (or later) no longer supports that version of Windows. Suppose you have a Velocity 3.5 Client running on Windows XP. In that case, you will have to either upgrade the operating system on that computer before upgrading the Velocity Client from 3.5 to 3.6 or replace that computer with one that has a supported version of Windows and perform a new installation of the Velocity 3.6 Client.
If you are running any 3.6 release, you should update to the 3.7/3.8.x release.
Starting with the Velocity 3.7 release, customers will need to obtain a software license when updating an existing system. Refer to section: Obtaining and Adding Velocity License.
Preparing to Upgrade
Before you start the upgrade process, you must perform these required tasks:
Back up your database before attempting any upgrade. Doing so enables you to return to an earlier working state if a mistake is made somewhere in the upgrade process.
Before updating to the latest Velocity release from a Velocity 3.7 release, you must register your Velocity software and obtain the necessary license(s). See the Velocity Licensing topic for details.
Existing Velocity users moving from 3.6 or 3.7 to 3.8.x use the Velocity Update Wizard. This wizard simplifies the effort required to upgrade and uses smaller installation files than the Upgrade Wizards provided for previous Velocity versions.
New installations of Velocity 3.8.6 provide you with the option to install the free Express edition of SQL Server 2019. Suppose this Express edition is not adequate for your needs. In that case, you must install a licensed edition of a supported version (2017, 2019 or 2022) of SQL Server before doing a new Server installation of Velocity 3.8.6.
If you already have SQL Server 2017, 2019 or 2022 installed on your server, the Velocity 3.8.6 Installer detects and uses your complete edition of SQL Server for the Velocity database.
Make sure the available Hard Disk free space is at least twice the size of your Velocity database. This requirement applies regardless of whether you have the Express edition of SQL Server or a licensed complete edition.
Make sure that you are logged in with an appropriate administrator account or have administrator privileges and have permission to update the Velocity Database.