Unimus can be deployed using an embedded file-based database (HSQL - only for small deployments), or a full dedicated DB.

You can find the full list of supported DB types and versions here.

Supported databases and versions

Recommended DB settings:

For optimal performance and compatibility of your database with Unimus you can find recommend DB settings it he following table.
In case your database use any other collation, please make sure to choose one that is always case-insensitive.

Using this combination ensures better global language support and consistent case-insensitive behavior in text comparisons.

HSQL (file-based) database considerations

Please note we do not recommend using the HSQL (file-based) database for deploys over 100 devices, and do not support HSQL deploys with 1000+ devices.

Since HSQL is a file based database, that keeps all data in a few flat text-based files, as the DB size grows, performance is severely impacted. If you want to use HSQL long-term, you should:

• setup data retention policies for both History Jobs and Backups (in "Other Settings")
• monitor database directory size (it should not reach multi-gigabyte sizes)
• monitor disk usage of the disk where HSQL stores its data

HSQL databases can get corrupted if the disk on which data is stored runs out of space.

PostgreSQL details

Unimus 2.5 and older support only PostgreSQL 11 and older. Unimus 2.6 added support for newer versions, and the table above shows the full supported range.

To upgrade an existing PostgreSQL database, see Upgrading the PostgreSQL database.