Migration from MSSQL to MariaDB
Microsoft SQL Server is no longer supported by Relution. With an MSSQL database, Relution aborts the start with the message Microsoft SQL Server databases are not supported by Relution.
The following instructions describe how to migrate a Relution installation in version 5.24.2 from MSSQL to MariaDB using the HeidiSQL GUI. If support is needed, it is available from the Relution Helpdesk Team.
Prerequisites
- Version: Relution 5.24.2 is the last version that runs on Microsoft SQL Server. Older installations are updated to 5.24.2 before the migration. The MariaDB schema (step 6,
--database-migration-only) is created with exactly the same version 5.24.2, not with 5.25.0 or later, because theDATABASECHANGELOGtable is not exported. Newer versions are installed only after the data import and the functional check have been completed successfully. The intermediate versions described under Update → must be observed. - MariaDB: Relution 5.24.2 requires at least MariaDB 10.5.2, current Relution versions require MariaDB 10.11. With an older MariaDB version, Relution aborts the start. MariaDB is only supported until the end of 2027, PostgreSQL is recommended (see System requirements →). For Docker installations, the subsequent switch is described under Migration from MariaDB to PostgreSQL →.
- Java: The environment variable
JAVA_HOMEis set. WithoutJAVA_HOME,relution-foreground.batexits without a message.
Migration
The migration takes place in two parts: first, Relution creates the schema in the new database, then the data is transferred with HeidiSQL.
Create the schema
Relution is shut down.
A MariaDB server is provided and the
my.cnfis configured (cnf template →).A new, empty database with the character set
utf8mb4and the collationutf8mb4_general_ciis created with HeidiSQL. The schema (tables and views) is not created manually, but by Relution in step 6.The old and the new database are connected in HeidiSQL.
In the
application.yml, the valuestype,url,usernameandpasswordunderrelution.databaseare changed to the new database:relution: database: type: mariadb url: jdbc:mariadb://<db_server>:3306/<db_name>?useServerPrepStmts=true username: <user> password: <password>Relution is started once against the new database so that only the database migration runs. For this purpose, the environment variable
RELUTION_ARGUMENTSis set in a command prompt in the Relution installation directory, andrelution-foreground.batis then started:set RELUTION_ARGUMENTS=--database-migration-only windows-bin\relution-foreground.batArguments appended directly to
relution-foreground.bathave no effect, because the script only passes the content ofRELUTION_ARGUMENTSon to Java. The variable only applies to this command prompt. After the run, the command prompt is closed orset RELUTION_ARGUMENTS=is executed so that Relution does not start in migration-only mode again later.Relution exits automatically once the schema has been created. The log is then checked to verify that the migration has completed without errors.
Transfer the data
The data is written directly from the old to the new database using the HeidiSQL export function.
- Right-click on the old database
- Database export
- The tables
DATABASECHANGELOG,DATABASECHANGELOGLOCKandJGROUPSPINGas well as all views are deselected - Max INSERT length to 10k
- Everything is deselected for databases and tables

- Output: new database server
- Database: new database
- Start of the migration
After the migration
- Relution is started.
- The Relution log is checked to verify that the start works correctly. The location of the log files is described under Relution Logs →.
- After logging in to Relution, it is checked whether resources can be loaded.
- Under
Devices→Inventory, it is checked whether the device list (database views) loads.