This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Note

: This feature is available in Enterprise, and Ultimate editions only.

Table of contents

• Add a Liquibase PRO key from the configuration file
• Add a Liquibase PRO key using preferences
• Enable PRO objects in schema compare

Liquibase PRO unlocks advanced database change tracking in DBeaver. With a valid PRO key, you can work with an extended set of database objects and generate richer, more detailed changelogs for your projects. This helps you describe structural changes more accurately and build safer, production-ready migration workflows.

In DBeaver, the Liquibase PRO key is used by Schema Compare and Liquibase changelog generation. Once you activate the key, these tools automatically include the additional metadata supported by Liquibase PRO.

Tip: If you only need basic schema comparison or simple changelogs, you can work without a PRO key. Use Liquibase PRO when your project requires deeper metadata coverage or more advanced migration logic.

Add a Liquibase PRO key from the configuration file

1. Locate your dbeaver.ini file. For help finding dbeaver.ini, see our article

2. Edit the file:

   • find the -vmargs command

   • add a new line after it:

     Example:

     -Dliquibase.license.key=ABwwGgQU...

3. Restart DBeaver

4. Open DBeaver, then open the Schema Compare tool. The key will be verified automatically

Note

: If you add the key in both dbeaver.ini and through the Import Key dialog, the .ini file key takes priority.

Add a Liquibase PRO key using preferences

You can also add the key directly in the UI:

1. Go to Preferences -> Editors -> Schema Compare
2. Use the Import Liquibase Pro Key button to open the import key dialog

Enable PRO objects in schema compare

If the license key is valid, the Object types dialog includes Pro objects:

• check constraints
• triggers
• stored procedures
• functions
• synonyms (Oracle)
• packages and package bodies (Oracle)

Tip: If Pro objects don’t appear in the changelog, check the logs. The key might be invalid or expired. Log rules come from the global Schema Compare settings, so make sure logging is enabled and set to a useful level.