Always back up your existing database before you upgrade HPD. |
From... | To... | Update Required |
|---|---|---|
4.0.17 | 4.1.0 | A schema upgrade is required. |
4.1.0 | 4.1.1 | A schema upgrade is optional. A schema upgrade is required for the following issues reported in the changes list: whitespace issues with profile names in HPD Catalogue Editor, 4.1.0 server upgrade patch failure and less round-trips to the database for new schema creation. |
4.1.1 | 4.1.2 | A schema upgrade is required. |
4.1.2 | 4.1.3 | A schema upgrade is not required. |
4.1.3 | 4.1.4 | A schema upgrade is not required. |
4.1.4 | 4.1.5 | A schema upgrade is required. |
4.1.5 | 4.1.6 | A schema upgrade is required. |
4.1.6 | 4.1.7 | A schema upgrade is required. |
4.1.7 | 4.1.8 | A schema upgrade is optional. The server changes in this release are for the HPD data pump. If sending a dump file to Customer Service, it is highly recommended to upgrade HPD before creating the dump file. |
4.1.8 | 4.1.9 | A schema upgrade is optional. The copy panel code has been updated to include the conversion_id for new panel version. A schema upgrade is needed to upgrade existing database charts. |
4.1.9 | 4.1.10 | A schema upgrade is required. |
4.1.10 | 4.1.12 | A schema upgrade is required. |
4.1.12 | 4.1.13 | A schema upgrade is required. |
4.1.13 | 4.1.14 | A schema upgrade is not required. |
4.1.14 | 4.1.15 | A schema upgrade is required. |
4.1.15 | 4.1.16 | A schema upgrade is required. |
4.1.16 | 4.1.17 | A schema upgrade is not required. |
4.1.17 | 4.1.18 | A schema upgrade is not required. |
4.1.18 | 4.1.19 | A schema upgrade is required. |
4.1.19 | 4.1.20 | A schema upgrade is required. |
4.1.20 | 4.1.21 | A schema upgrade is required. |
4.1.21 | 4.1.22 | A schema upgrade is not required. |
4.1.22 | 4.1.23 | A schema upgrade is required. |
4.1.23 | 4.1.24 | A schema upgrade is required. |
4.1.24 | 4.1.25 | A schema upgrade is not required. |
4.1.25 | 4.1.26 | A schema upgrade is required. |
4.1.26 | 4.1.27 | A schema upgrade is required. |
4.1.27 | 4.1.28 | A schema upgrade is required. |
4.1.28 | 4.1.29 | A schema upgrade is required. |
4.1.29 | 4.1.30 | A schema upgrade is optional, but is needed to see the improved processing time when opening an HPD database view, to no longer see hash tags for large product version IDs when running updateVector SQL scripts, and to get the update for setting edition numbers (EDITION) with the SET_PRODUCT_ATTRIBUTE API function. |
4.1.30 | 4.1.31 | A schema upgrade is not required. |
4.1.31 | 4.1.32 | A schema upgrade is not required. A schema upgrade is needed if you require the HPD API to restrict values when setting the panel number (PANNUM) attribute, and/or to see a performance improvement for the HPD server |
4.1.32 | 4.1.33 | A schema upgrade is not required, but is needed to update the database catalogue for expanded vertical datum (VERDAT) values. |
4.1.33 | 4.1.34 | A schema upgrade is not required. |
4.1.34 | 4.1.35 | A schema upgrade is required. |
4.1.35 | 4.1.36 | A schema upgrade is required. The upgrade accelerates the opening of the Product Boundaries layer in Source Editor. |
4.1.36 | 4.137 | A schema upgrade is required. |
4.1.37 | 4.1.38 | A schema upgrade is optional, but is needed to use the improved optimize_space.sql script. |
4.1.38 | 4.1.39 | A schema upgrade is required. |
4.1.39 | 4.1.40 | A schema upgrade is not required. |
4.1.40 | 4.1.41 | A schema upgrade is optional, but is required if a data pump is being created. |
4.1.41 | 4.1.42 | A schema upgrade is not required. |
4.1.42 | 4.1.43 | A schema upgrade is required. |
4.1.43 | 4.1.44 | A schema upgrade is not required. |
4.1.44 | 4.1.45 | A schema upgrade is not required, but is needed for specific changes. |
4.1.45 | 4.1.46 | A schema upgrade is required. |
4.1.46 | 4.1.47 | A schema upgrade is required if updating the ENC 3.1 database catalogue for changes to S-58 Test 507. |
4.1.47 | 4.1.48 | A schema upgrade is not required. |
4.1.48 | 4.1.49 | A schema upgrade is not required. 4.1.49 is the final release of the 4.1.x series. Users are encouraged to upgrade to the 5.0.x series for the latest developments. |