Important Information for 7.0.0 Upgrades
- Matthew Garrett
7.0.0 Upgrade Prerequisite
The v7.0.0 upgrade now requires a minimum database Compatibility level of SQL Server 2005 (90).
CRITICAL
This must be done prior to commencing the Upgrade
To check or set this using Microsoft SQL Server Management Studio
Launch Properties dialog
Select the Options page
Check the Compatibility level selection and adjust to SQL Server 2005 (90) as a minimum.
This should be checked on any database that will be upgraded.
6.3.0 Upgrade Sequence
Depending on the version of Framework applications currently installed, there may be a number of database upgrades that need to be performed to bring the Framework databases up to version 6.3.0. It is important to note that each upgrade MUST be run individually.
The following table lists the database upgrades that MUST be performed for the Framework Product Suite applications, depending on the currently installed version.
Currently Installed Version | Framework ECM | Framework Logistics Tablet | Framework Sales Advice Management | Framework MyNewHome |
|---|---|---|---|---|
4.7.0 | 5.0.0 | 5.0.0 | 5.0.0 | 5.0.0 |
5.0.0 | 5.1.0 5.1.1 5.1.2 | 5.1.0 5.1.1 5.1.2 | 5.1.0 5.1.1 | 5.1.0 |
5.1.2 | 5.2.0 | 5.2.0 | 5.2.0 | 5.2.0 |
5.2.0 | 5.3.0 5.3.1 5.3.2 | 5.3.0 5.3.1 5.3.2 | 5.3.0 | 5.3.0 |
5.3.2 | 5.4.0 5.4.1 5.4.2 | 5.4.0 5.4.1 5.4.2 | 5.4.0 5.4.1 | 5.4.0 * |
5.4.2 | 6.0.0 | 6.0.0 | 6.0.0 | 6.0.0 |
6.0.0 | 6.1.0 | 6.1.0 | 6.1.0 | 6.1.0 |
6.1.0 | 6.2.0 | 6.2.0 | 6.2.0 | 6.2.0 |
6.2.0 | 6.3.0.xx | 6.3.0.xx | 6.3.0.xx | 6.3.0.xx |
6.3.0 | 7.0.0.xx | 7.0.0.xx | 7.0.0.xx | 7.0.0.xx |
* The Framework ECM database must be upgraded to v5.4.2 before the Framework MyNewHome v5.4.0 upgrade can be started.
Example: If your current version of Framework Logistics Tablet is v5.1.2, then you would need to run the following Framework Logistics Tablet database upgrade executable files:
- 5.2.0
- 5.3.0
- 5.3.1
- 5.3.2
- 5.4.0
- 5.4.1
- 5.4.2
- 6.0.0
- 6.1.0
- 6.2.0
- 6.3.0
Refer to the individual upgrade guides for specific information on how to execute each upgrade.
It is important that a backup of the database is taken before each upgrade commences, in case the upgrade fails and the database needs to be rolled back.
Upgrade Version
From Upgrade version 6.3.0 onwards, there is a further versioning number, for example 6.3.0.30. There is no change to the way the upgrades are run, except that each individual upgrade run should have the same full version number.