For the SettingKey version it behaves exactly as described in the point FM_version. In the delivery package there is the order SmartNotes_2.x_Update with the following files: - UPDATE SmartNotes 2017-10-18 TO 2.5.0.4 (2018-01-22).sql
- UPDATE SmartNotes 2018-01-22 TO 2.5.0.10 (2018-04-12).sql
- UPDATE SmartNotes 2018-04-12 TO 2.5.0.12 (2018-04-17).sql
- UPDATE SmartNotes 2018-04-17 TO 2.5.0.20 (2018-08-18).sql
- UPDATE SmartNotes 2018-08-18 TO 2.5.0.26 (2018-12-05).sql
- UPDATE SmartNotes 2018-12-05 TO 2.5.0.30 (2019-04-04).sql
- UPDATE SmartNotes 2019-04-04 (2.5.0.30) TO 2.6.0.0 (2018-12-05).sql
- UPDATE SmartNotes 2018-12-05 TO 2.6.0.3 (2019-03-18).sql
- UPDATE SmartNotes 2019-03-18 TO 2.6.0.9 (2019-04-04).sql
- UPDATE SmartNotes 2019-04-04 TO 2.6.0.15 (2019-06-18).sql
- UPDATE SmartNotes 2019-06-18 TO 2.6.0.19 (2019-07-08).sql
- UPDATE SmartNotes 2019-07-08 TO 2.6.0.21 (2019-08-14).sql
- UPDATE SmartNotes 2019-08-14 TO 2.6.0.30 (2020-01-21).sql
- Create SmartNotes FACTORY for MSSQL 2008 v2.6 2018-10-22.sql (can be found in the delivery package)
- This script is to be executed, if the FM_version step was skipped
- UPDATE SmartNotes for MSSQL v2.x.x.xx yyyy-mm-dd.sql
For example, if the SettingKey version from the TSYSTEM is 2018-12-05 and the version is 2.5.0.26, then scripts 6-13 would be executed, then 14 if necessary, and 15 as the last script. If the SettingKey version from the TSYSTEM is for example 2019-06-18, then scripts 11-13 would be executed, then if necessary 14 and as the last script 15. Note |
---|
The numbered scripts are to be executed exactly in this order! |
|