...
You will need to execute these scripts from the version of FlexDeploy you currently have, up to the latest version. And they must be executed in that order. For example, See examples below if you are upgrading from FlexDeploy 3.7.1 to FlexDeploy 4.5.0 or FlexDeploy 4.0.0 to FlexDeploy 4.5.0, you will need to execute .
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
migration3.7.1_to_4.0.0.sql |
...
migration4.0.0_to_4.0.1.sql |
...
migration4.0.1_to_4.0.2.sql |
...
migration4.0.2_to_4.0.3.sql |
...
migration4.0.3_to_4.5.0.sql |
...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
migration3migration4.70.10_to_4.0.01.sql migration4.0.01_to_4.0.12.sql migration4.0.12_to_4.0.23.sql migration4.0.23_to_4.5.0.3.sql |
The migration4.0.
...
2_to_4
...
.0.3.sql file includes all of the 403PatchRelease*.sql files in it. Patch Release SQL files are only necessary if you are on a 4.0.
...
3 Patch Release.
If you are upgrading from a 4.0.3 Patch Release, follow the date based SQL files in sequence by Date. If you have already a applied specific Patch Release patch then skip it. You can make determination of which Patch Release files to run by looking at Build Time on the About window of your FlexDeploy installation. After completing the last 403PatchRelease, run the migration4.0.3_to_4.5.0.sql file. Contact Flexagon support for details if you are not sure. See example below.
...