...
The v7.0.0 upgrade now requires a minimum database Compatibility level of SQL Server 2005 (90).Critical :
| Warning | ||
|---|---|---|
| ||
This must be done prior to commencing the Upgrade |
To check or set this using Microsoft SQL Server Management Studio
...
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 |
...
Refer to the individual upgrade guides for specific information on how to execute each upgrade.
...
| Warning |
|---|
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.