Upgrade Guide¶
MIKE OPERATIONS
This guide explains how to upgrade a MIKE OPERATIONS system to release 2025.2.
Note
In this document, MIKE OPERATIONS will refer specifically to the 2025.2 version. For information about upgrading to other versions, please read the corresponding guides.
It is recommanded to have a test and a production system to decrease the upgrade risk and improve the uptime of the system. When upgrading a system, several components should be considered:
- Operating system upgrade and security patching
- Database server upgrade
- Modelling Software upgrade and model update
- MIKE OPERATIONS Software upgrade
- MIKE OPERATIONS Database update
- Acceptance testing (i.e. ensure the system still performs as expected)
In this page, we will focus on 2, 3, 4 and 5.
1. Update database server¶
When upgrading a MIKE OPERATIONS system, the first thing to consider is whether or not to upgrade the database server.
A general recommendation is to use the latest version supported by MIKE OPERATIONS (i.e. 17.4). However, when older versions are still supported by the PostgreSQL Global Development Group they are also supported in MIKE OPERATIONS, as shown in the table below. So upgrading the database is not compulsory in those cases. PostgreSQL versions accepted by MIKE OPERATIONS can also be viewed in the file DssDatabases.cfg.xml of the MIKE OPERATIONS installation folder.
| Supported Database version | Corresponding PostGIS |
|---|---|
| PostgreSQL 17 | PostGIS 3.5.* |
| PostgreSQL 16 | PostGIS 3.4.* |
| PostgreSQL 15 | PostGIS 3.4.* |
| PostgreSQL 15 | PostGIS 3.3.* |
| PostgreSQL 14 | PostGIS 3.3.* |
| PostgreSQL 14 | PostGIS 3.2.* |
| PostgreSQL 14 | PostGIS 3.1.* |
| PostgreSQL 13 | PostGIS 3.2.* |
| PostgreSQL 13 | PostGIS 3.1.* |
| MS SQL 2022 | N/A |
| MS SQL 2019 | N/A |
| SQlite | N/A |
Depending on the database you have installed, and considering the table above, 3 possibilities exist.
| Existing database server | Description | Action |
|---|---|---|
| Not supported | The database is not supported by PostgreSQL | Install PostgreSQL 17.4 (see installation guide) |
| Supported (not latest) | The database version is supported by PostgreSQL but not the latest | Install latest minor version (e.g. from PostgreSQL 14.0 to PostgreSQL 14.18) following guidelines |
| Supported (latest) | The database version is the latest | Install latest minor version (e.g. from PostgreSQL 17.3 to PostgreSQL 17.4) following installation guide |
Note
Make sure to have a PostGIS version consistent with the PostgreSQL (see table). Combinations of later versions may also work but have not been tested.
2. Run installer¶
Run the exe file¶
Minor versus Major upgrade
When upgrading minor versions (e.g. from 2025.0 to 2025.2), the MIKE OPERATIONS installation will be overwritten and no uninstallation will be required. If the runtime.config file holds customisation, a copy will be made. When upgrading major version (e.g. from 2023.3 to 2025.2), both versions will be available side by side. The older version should be manually delete.
MIKE OPERATIONS is installed by running setup.exe as administrator to allow all components to be installed.
Warning
Do not run the MIKE OPERATIONS 2025.msi file.
This will update the prerequisites.
Accept the license agreement¶
Read and accept the license agreement and click Next.
Select Components¶
Job Service Port¶
Specify the port to use for the Job Manager Service.
Use the default port (8089).
It’s possible in this step, to specify a computer user profile to be used when running jobs. This can also be edited after the installation..
Note
If the Job Manager fails to start, this might be because the default port used for the Job Manager Service is already used.
In that case, please restart the installation process and select a different port number.
Click Next
Note
To install the job service on another computer for remote exexution, read this page
PostgreSQL administrator password¶
If you’ve selected a PostgreSQL installation, you will be asked to provide a password for PostgreSQL database service.
Provide a new Password to the PostgreSQL database service (or the existing password if the PostgreSQL database service is upgraded).
Info
Remember this password as the password should be used whenever the MIKE OPERATIONS Database Manager Utility is used or when the PostgreSQL native database management software pgAdmin is applied.
Click Next
Install¶
Click Install
This will install will MIKE OPERATIONS in C:\Program Files (x86)\DHI\MIKE OPERATIONS\2025\bin.
Finish Installation¶
Click Finish
PostgreSQL Installation¶
If you are doing a PostgreSQL installation, wait until installation of PostgreSQL and PostGIS is complete.
Click OK to complete the installation once the PostgreSQL installation is complete.
DHI License File¶
The DHI license is handled through the DHI License Management software, which can be found under DHI License Administration in the Start Menu.
Open the DHI License Management program in the start menu as administrator.
There three different options: - Internet License - Network License - Local License (dongle)
Note
All Users must be ticked to allow job execution (if job service is using another user profile)
Please refer to the Trouble shooting section of the Job Manager documentation or contact your local MIKE Sales representative.
3. Updating the database¶
From one version to another one, the database schema usually evolved. When upgrading to a newer version, we need to also upgrade the database.
Back up database¶
The current database should be backed-up, using the MIKE OPERATIONS Database Manager Utility.
Restore to new database server (optional)¶
Following the consideration in Chapter 1, if a new database server was installed, the database file should be then restored, using the MIKE OPERATIONS Database Manager Utility.
Update database¶
The database must then be updated, using the the MIKE OPERATIONS Database Manager Utility.
Note
After updating the database, MIKE OPERATIONS users working with the earlier version of the software will not be able to use the database. After the database has been updated everybody using the database should update the client.
4. Update modelling software version(s) (optional)¶
If the current system has model(s) registered in the Scenario Manager, you should first check in what version they were registered. To do so, you have several options - Check the release notes of the MIKE OPERATIONS version you have installed and find the modelling version that was supported at that time - Open the model in Native Tools and investigate in which
| Native tool | MIKE SHE example |
|---|---|
 |
 |
Then compare with the supported version.
The different options are summarized in the table below
| Model version | Example | Action |
|---|---|---|
| Current version supported | Update a MIKE OPERATIONS 2025.0 system | Do nothing, the registered model will still run |
| Current version not supported | Update a MIKE OPERATIONS 2024.0 system running MIKE+ | Update model following guidelines |
| Current software decommissioned | Update a MIKE OPERATIONS 2022.0 system running MIKE HYDRO River | A convertion of your model to newer software might be required, contact your local support team |
5. Add customisation (optional)¶
If you have made custom tools or extensions, read this page to learn how to enable them in this new version of MIKE OPERATIONS.
6. Test¶
To make sure that the installation was successful, several checks should be carried out - Run the Troubleshooting Wizzard. - Run your model(s) manually - Run your jobs manually
7. Delete older version¶
Once you are confident that the new system works as expected, you can delete the old version version of MIKE OPERATIONS and, if applicable, the PostgreSQL database server.