Migration not happening and no log output

Which version and edition of Flyway are you using?

<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-core</artifactId>
    <version>6.1.3</version>
</dependency>

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)

It is used inside a Java Spring Boot application. Imported through maven.

Which database are you using (type & version)?

The problematic database is an mssql server 2017 (as far as I know)

Which operating system are you using?

I am using Linux, but the application is also running on Windows and throwing the error there too.

What did you do?

(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.) I started to use flyway to migrate all persistent databases to a newer Camunda version.

I’ve written a code snippet which determines the current database version and then baselines and migrates if necessary, using Flyway. On PostgreSQL and h2 the migration works fine… Using the mssql server is the only problem:

On start, My code realizes the database still uses an older camunda version and configures flyway and prepares for a migration. Logging get’s up to 1 or 2 lines before the baseline and migrate but then just stops without any notice…

log.info("Version table wasn't found.. Baselining version 1 and using flyway to migrate to the current version");
flyway = flywayConfiguration.baselineVersion("1").load();
flyway.baseline();
flyway.migrate();
log.info("Database migration done");

This is the code… And the configuration is correct (loaded from the camunda process engine which has a working connection) the first line is shown in the logs… And the log file is also showing that Flyway has been initialized. After the first info log flyway just stops… baseline doesn’t even happen

What did you expect to see?

I expected to see flyway attempting a migration and either throw an error or logging a successful migration/writing the flyway_schema_log table

What did you see instead?

Nothing.

[StoffelCPR]

Okey. I got the error of the server…

It seems like the logger is misconfigured, because if I try the smelly version of testing with my machine against the SQL Server the following log output appears: Flyway Enterprise Edition or SQL Server upgrade required: SQL Server 2012 is no longer supported by Flyway Community Edition, but still supported by Flyway Enterprise Edition.

**EDIT Our file logger seems to miss this error.

If executed in a terminal the error shows up. so This issue is not an issue…

[StoffelCPR]

Thanks for your quick help 😉