| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Article Index
| Table of Contents |
|---|
Depending on the version of Framework applications of Framework applications currently installed, there may be a number of database upgrades that need to be performed to bring the Framework databases the Framework databases up to version 7.1.1.
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 the Framework Product Suite applications, depending on the currently installed version.
From | To | Run Framework Upgrade: | |||
|---|---|---|---|---|---|
Current Version | New Version | ECM | Logistics Tablet | Sales Advice | MyNewHome |
6.0.0 | 6.1.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.2.0 | 6.3.0 | 6.3.0.38 | 6.3.0.38 | 6.3.0.38 | 6.3.0.38 |
6.3.0 | 7.0.0 | 7.0.0.36 | 7.0.0.36 | 7.0.0.36 | 7.0.0.36 |
7.0.0.36 | 7.1.1 | 7.1.0.23 7.1.1.06 | 7.1.0.23 7.1.1.06 | 7.1.0.01 7.1.1.03 | n/a |
For earlier versions, please see Important Information for 7.0.0 Upgrades.
Important Considerations
Compatibility
From v7.0.0 the upgrade requires a minimum database Compatibility level of SQL Server 2005 (90).
| Warning |
|---|
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. If the Compatiblity is not set, the upgrade will fail to run.
Backups
The ECM upgrade used to have a backup option inbuilt. From 7.0.0 this is no longer the case.
| 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 Versioning
From Upgrade version v6.3.0 onward, there is a further versioning number called the Build Number, for example 6.3.0.30.
...