> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/troubleshooting/databases/flyway_version.md).

# Flyway version issue

The Flyway error that stops an installation on SQL Server, which reports an edition problem but means the database version is below the supported floor.

| Symptom                                                                           | Likely cause                                           | Resolution                |
| --------------------------------------------------------------------------------- | ------------------------------------------------------ | ------------------------- |
| The installation stops with `Flyway Teams Edition or SQL Server upgrade required` | The SQL Server instance is older than OpenIAM supports | Upgrade SQL Server, below |

The database initialization stops and the migration tool reports:

{% code overflow="wrap" %}

```
ERROR: Flyway Teams Edition or SQL Server upgrade required: SQL Server 2016 is no longer supported by Flyway Community Edition, but still supported by Flyway Teams Edition.
```

{% endcode %}

The lines above it in the output are the driver's own connection-property dump, which is normal and not part of the fault. The `ERROR` line is the whole message.

## What it actually means

The error offers two ways out — a paid Flyway edition, or a newer SQL Server — and reads as though either would do. For OpenIAM only one of them applies.

{% hint style="warning" %}
**SQL Server 2016 is below the supported version.** OpenIAM requires **SQL Server 2019 or later** — see [System requirements](/installation/system-requirements.md). The Flyway message is the first place that shows up, because database initialization is the first thing that touches the server.
{% endhint %}

## Resolution

**Upgrade the SQL Server instance to 2019 or later**, then run the installation again.

{% hint style="danger" %}
**Do not downgrade Flyway to work around this.** Older Flyway releases accept SQL Server 2016, and an earlier version of this page suggested 6.5.4 — but that only moves the failure. The result is a deployment running on an unsupported database, with a migration engine older than the schema migrations shipped against it. Neither is supportable.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openiam.com/troubleshooting/databases/flyway_version.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.