For the complete documentation index, see llms.txt.
Skip to main content
Version: 8.9

Access SQL and Liquibase scripts

Access and safely use the SQL and Liquibase scripts provided with Camunda 8 for supported databases. These scripts can be used for provisioning, upgrading, or managing database schemas in your environment.

Related pages

Where the scripts are published​

The scripts are included in the Camunda 8 Run distribution and in each Camunda GitHub release as a versioned ZIP file:

  • GitHub release example: Camunda 8.9.0
  • C8Run distribution: top-level folder rdbms-schema/

Distribution & ZIP contents​

The ZIP contains SQL scripts and Liquibase change sets for all supported databases:

/ -
| liquibase
  - changelog-master.xml
  | changesets
    - 8.9.0.xml
    - 8.10.0.xml
| sql
  | create
    | h2
      - h2_create_8.9.0.sql
    | mariadb
      - mariadb_create_8.9.0.sql
    | mssql
      - mssql_create_8.9.0.sql
    | mysql
      - mysql_create_8.9.0.sql
    | oracle
      - oracle_create_8.9.0.sql
    | postgresql
      - postgres_create_8.9.0.sql
  | upgrade
    | h2
      - h2_upgrade_8.9.0_to_8.10.0.sql
    ...
note

Drop scripts are not provided.

How to download​

  • From a GitHub release (ZIP): Download the schema scripts from https://github.com/camunda/camunda/releases/tag/<release version>/camunda-db-rdbms-schema-<release version>.zip.
  • From a C8Run distribution: Retrieve the schema scripts from the rdbms-schema/ folder included in the distribution.

Usage guidance​

  • Version matching: Always use scripts corresponding to your Camunda 8 version.
  • Database selection: Use the folder for your target database (PostgreSQL, Oracle, MariaDB, MySQL, SQL Server, or H2).
  • Automatic schema management: Camunda will manage the schema by default. Manual management requires disabling auto-DDL:
camunda:
  data:
    secondary-storage:
      rdbms:
        auto-ddl: false
  • SQL vs. Liquibase: Liquibase changelogs are forward-only. Rollbacks are not supported.
warning

Do not mix SQL upgrade scripts with Liquibase-managed schema. Applying SQL scripts to a Liquibase-managed schema causes checksum mismatches and schema inconsistencies.

  • Liquibase lock recovery: If a pod is interrupted during Liquibase execution, Camunda waits for stale DDL locks using camunda.data.secondary-storage.rdbms.ddl-lock-wait-timeout (default: PT15M). Increase this timeout for long-running migrations and only release databasechangeloglock manually after confirming no migration is running. See RDBMS troubleshooting.
  • Backup first: Always back up your database before applying scripts manually.

Additional resources​

  • Checksums: SHA1 or SHA256 checksums are provided in GitHub release assets.
  • Liquibase CLI example: See Liquibase getting started.
  • Upgrade workflow: Recommended approach is to allow Camunda to manage the schema automatically. Manual upgrades are supported, but users must apply scripts sequentially from the initial version to the target version.
  • Performance: Indexes are included in scripts as needed. Adding custom indexes may affect future upgrades.