Skip to content

Supported Databases

MIKE OPERATIONS supports the following relational database databases.

  • PostgreSQL
  • Microsoft SQL Server
  • SQLite

Where both PostgreSQL and SQL Server are client/server SQL database engines, SQLite is a local data storage. SQLite is inteded for single user installations and for test or demonstration setups.

PostgreSQL

MIKE OPERATIONS supports PostgreSQL database versions until the database versions are desupported by the PostgreSQL Global Development Group (PGDG).

This means that a PostgreSQL database version cannot be used with a version of MIKE OPERATIONS released after the PostgreSQL database version has been desupported by PGDG.

Read more about PostgreSQL versions supported by PGDG and their versions policies here.

Download the latest Windows installers for PostgreSQL from EDB here

New major versions of PostgreSQL are usually released every year in August or September.

Minor versions of PostgreSQL are usually released every quarter (August, November, February and May).

MIKE OPERATIONS most likely support new major releases of PostgreSQL with major release of MIKE OPERATIONS.

The MIKE OPERATIONS installer comes with a (default) version of PostgreSQL. The version included will be upgraded to a new major as soon as the first minor of PostgreSQL has been released

This means that the following version of PostgreSQL are expected to be included with the installer:

Month Officiel MO Release Minor MO PostgreSQL version
November Yes 0 <major>.4
February No 1 <major>.1
May Yes 2 <major>.2
August No 3 <major>.3

This means that a new major version of PostgreSQL is usually included in the installer of the internal February release of MIKE OPERATIONS.

Note

PostgreSQL is the recommended choice of database for MIKE OPERATIONS.

PostGIS

PostGIS is an extension to PostgreSQL for storing and managing spatial information. The PostGIS extension is required by MIKE OPERATIONS to store and display spatial data.

Read more about the PostGIS extension on postgis.net.

The Open Source Geospatial Foundation is releasing PostGIS versions for Windows.

Installers for Windows can be found here.

When a new PostGIS version is released, MIKE OPERATIONS will support the PostGIS version with the next release of MIKE OPERATIONS so that the new PostGIS version can be used with the two latest major releases of PostgreSQL.

PostgreSQL Version Support

The table below shows the PostgreSQL and PostGIS versions supported by the various MIKE OPERATIONS versions.

MIKE OPERATIONS PostgreSQL (PostGIS) Note
2025.2
  • 17 (3.5)
  • 16 (3.4)
  • 15 (3.3, 3.4)
  • 14 (3.3, 3.2, 3.1)
  • 13 (3.2, 3.1)
    		•
    2025.1
  • 17 (3.5)
  • 16 (3.4)
  • 15 (3.3, 3.4)
  • 14 (3.3, 3.2, 3.1)
  • 13 (3.2, 3.1)
    		•
    2025
  • 17 (3.5)
  • 16 (3.4)
  • 15 (3.3, 3.4)
  • 14 (3.3, 3.2, 3.1)
  • 13 (3.2, 3.1)
    		•  PostgreSQL 12 has been desupported with this version.
    2024.3
  • 16 (3.4)
  • 15 (3.3, 3.4)
  • 14 (3.3, 3.2, 3.1)
  • 13 (3.2, 3.1)
  • 12 (3.0)
    		•
    2024.2
  • 16 (3.4)
  • 15 (3.3, 3.4)
  • 14 (3.3, 3.2, 3.1)
  • 13 (3.2, 3.1)
  • 12 (3.0)
    		•
    2024.1
  • 16 (3.4)
  • 15 (3.3, 3.4)
  • 14 (3.3, 3.2, 3.1)
  • 13 (3.2, 3.1)
  • 12 (3.0)
    		•  PostgreSQL 11 has been desupported with this version.
    2024
  • 16 (3.4)
  • 15 (3.3, 3.4)
  • 14 (3.3, 3.2, 3.1)
  • 13 (3.2, 3.1)
  • 12 (3.0)
  • 11 (2.5.3, 2.5.2, 2.5.1, 2.5.0)
    		•
    2023.3 (obsolete)
  • 15 (3.3)
  • 14 (3.3, 3.2, 3.1)
  • 13 (3.2, 3.1)
  • 12 (3.0)
  • 11 (2.5.3, 2.5.2, 2.5.1, 2.5.0)
    		•
    2023.2
  • 15 (3.3)
  • 14 (3.3, 3.2, 3.1)
  • 13 (3.2, 3.1)
  • 12 (3.0)
  • 11 (2.5.3, 2.5.2, 2.5.1, 2.5.0)
    		•  Azure Database for PostgreSQL Single Server is no longer supported by Microsoft as well as MIKE OPERATIONS. Please upgrade to Flexible Server.
    2023.1
  • 15 (3.3)
  • 14 (3.3, 3.2, 3.1)
  • 13 (3.2, 3.1)
  • 12 (3.0)
  • 11 (2.5.3, 2.5.2, 2.5.1, 2.5.0)
    		•  PostgreSQL 10 has been desupported with this version.
    2023
  • 14 (3.2, 3.1)
  • 13 (3.2, 3.1)
  • 12 (3.0)
  • 11 (2.5.3, 2.5.2, 2.5.1, 2.5.0)
  • 10 (2.4.4, 2.4.3, 2.4.1)
    		•  Support for Azure Database for PostgreSQL - Flexible Server
    2022.1
  • 14 (3.2, 3.1)
  • 13 (3.2, 3.1)
  • 12 (3.0)
  • 11 (2.5.3, 2.5.2, 2.5.1, 2.5.0)
  • 10 (2.4.4, 2.4.3, 2.4.1)
    		•  From MIKE OPERATIONS 2022.1, all patch versions of a certain minor version of PostGIS are supported (after PostGIS 3.*). Support for Azure Database for PostgreSQL - Single Server
    2022
  • 14 (3.1.4)
  • 13 (3.1.4, 3.1.1, 3.1.0)
  • 12 (3.0.2, 3.0.1, 3.0.0)
  • 11 (2.5.3, 2.5.2, 2.5.1, 2.5.0)
  • 10 (2.5.3, 2.5.2, 2.5.1, 2.5.0, 2.4.4, 2.4.3, 2.4.1)
    		•  PostgreSQL 9.6 has been desupported with this version.
    2021.1
  • 13 (3.1.1, 3.1.0)
  • 12 (3.0.2, 3.0.1, 3.0.0)
  • 11 (2.5.3, 2.5.2, 2.5.1, 2.5.0)
  • 10 (2.5.3, 2.5.2, 2.5.1, 2.5.0, 2.4.4, 2.4.3, 2.4.1)
  • 9.6 (2.5.3, 2.5.1, 2.4.4, 2.4.1, 2.3.2, 2.3.1, 2.3.0)
    		•  PostgreSQL 9.5 has been desupported with this version.
    2021
  • 12 (3.0.2, 3.0.1, 3.0.0)
  • 11 (2.5.3, 2.5.2, 2.5.1, 2.5.0)
  • 10 (2.5.3, 2.5.2, 2.5.1, 2.5.0, 2.4.4, 2.4.3, 2.4.1)
  • 9.6 (2.5.3, 2.5.1, 2.4.4, 2.4.1, 2.3.2, 2.3.1, 2.3.0)
  • 9.5 (2.2.1)
    		•  From MIKE OPERATIONS 2021, all minor versions of a major PostgreSQL version (from PG v10) are supported.
    2020.2
  • 12.1 (3.0.0)
  • 11.6 (2.5.3, 2.5.1)
  • 11.5 (2.5.3)
  • 11.4 (2.5.2)
  • 11.2 (2.5.2)
  • 11.1 (2.5.1, 2.5.0)
  • 10.11 (2.5.3)
  • 10.10 (2.5.3)
  • 10.9 (2.5.2)
  • 10.7 (2.5.2)
  • 10.6 (2.5.1, 2.5.0)
  • 10.5 (2.5.0)
  • 10.4 (2.4.4)
  • 10.3 (2.4.4, 2.4.3)
  • 10.0 (2.4.4, 2.4.0)
  • 9.6 (2.5.1, 2.4.4, 2.4.1, 2.3.2, 2.3.1, 2.3.0)
  • 9.5 (2.2.1)
    		•
    2020.1
  • 11.6 (2.5.3)
  • 11.5 (2.5.3)
  • 11.4 (2.5.2)
  • 11.2 (2.5.2)
  • 11.1 (2.5.1, 2.5.0)
  • 10.11 (2.5.3)
  • 10.10 (2.5.3)
  • 10.9 (2.5.2)
  • 10.7 (2.5.2)
  • 10.6 (2.5.1, 2.5.0)
  • 10.5 (2.5.0)
  • 10.4 (2.4.4)
  • 10.3 (2.4.4, 2.4.3)
  • 10.0 (2.4.4, 2.4.0)
  • 9.6 (2.5.1, 2.4.4, 2.4.1, 2.3.2, 2.3.1, 2.3.0)
  • 9.5 (2.2.1)
    		•  PostgreSQL 9.4 has been desupported with this version.
    2020
  • 11.5 (2.5.3)
  • 11.4 (2.5.2)
  • 11.2 (2.5.2)
  • 11.1 (2.5.1, 2.5.0)
  • 10.10 (2.5.3)
  • 10.9 (2.5.2)
  • 10.7 (2.5.2)
  • 10.6 (2.5.1, 2.5.0)
  • 10.5 (2.5.0)
  • 10.4 (2.4.4)
  • 10.3 (2.4.4, 2.4.3)
  • 10.0 (2.4.4, 2.4.1)
  • 9.6 (2.5.1, 2.4.4, 2.4.1, 2.3.2, 2.3.1, 2.3.0)
  • 9.5 (2.2.1)
  • 9.4 (2.1.8)
    		•
    2019.2
  • 11.2 (2.5.2)
  • 11.1 (2.5.1, 2.5.0)
  • 10.10 (2.5.3)
  • 10.9 (2.5.2)
  • 10.7 (2.5.2)
  • 10.6 (2.5.1, 2.5.0)
  • 10.5 (2.5.0)
  • 10.4 (2.4.4)
  • 10.3 (2.4.4, 2.4.3)
  • 10.0 (2.4.4, 2.4.1)
  • 9.6 (2.5.1, 2.4.4, 2.4.1, 2.3.2, 2.3.1, 2.3.0)
  • 9.5 (2.2.1)
  • 9.4 (2.1.8)
    		•

    Microsoft SQL Server (MSSQL)

    Microsoft SQL Server is a relational database management system developed by Microsoft.

    With MIKE OPERATIONS 2020.1, Microsoft SQL Server is supported by MIKE OPERATIONS.

    Spatial Data in SQL Server

    Microsoft SQL Server does not require a spatial extension.

    Note that when using Microsoft SQL Server with MIKE OPERATIONS, it is only possible to store and display vector data (feature class). Raster data and meshes cannot be stored in the SQL Server database. This means that when using the MS SQL Server, remote spatial providers should be used.

    • MIKE Cloud Spatial Providers (from MIKE OPERATIONS 2022.1)
    • Remote dfs2 provider
    • Remote dfsu provider (from MIKE OPERATIONS 2023.1)

    SQLite

    SQLite is a C-language library that implements a small, fast, self-contained, high-reliability, full-featured, SQL database engine.

    Note

    SQLite can be used with MIKE OPERATIONS in a single user environent as it is not suited for environment with multiple users.

    Spatialite

    Spatialite is an open source library intended to extend the SQLite core to support fully fledged Spatial SQL capabilities. Using SQLite + SpatiaLite you can effectively deploy an alternative open source Spatial DBMS roughly equivalent to PostgreSQL + PostGIS.

    MIKE OPERATIONS is using the mod_spatialite extension module.