...
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 or 3.8 to 3.8.1 or 3.8.1 to 3.8.2/3.8.3/3.8.4/3.8.5/3.8.6.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.
...
Existing Velocity users moving from 3.6 or 3.7 to 3.8/3.8.1/3.8.2/3.8.3/3.8.4/3.8.5/3.8.6 .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.
...
If you are running any 3.6 release, you should update to the 3.7/3.8/3.8.1/3.8.2/3.8.3/3.8.4/3.8.5/3.8.6 .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.
...
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 / 3.8.1 /3.8.2 /3.8.3/3.8.4 /3.8.5/3.8.6 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 20192022) of SQL Server before doing a new Server installation of Velocity 3.8.6.
If you already have SQL Server 2017, 2019 or 2019 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.