New Webinar: Govern roles, shares, and data movement in Snowflake

Learn how to govern Snowflake roles, shares, and data movement without slowing delivery. Join our live webinar on controlling drift, permissions, and audit readiness.

Save your spot

dbms

Last updated: September 2, 2025

The dbms attribute is a string that specifies which database Liquibase should run a changeset on. dbms accepts "short names" of database management systems.

Valid values include all, none, and the following values, which correspond with supported databases:

  • all: allow this change to deploy to all supported databases

  • none: allow this change to deploy nowhere

  • aerospike

  • asany

  • bigquery

  • cassandra

  • cloudspanner

  • cockroachdb

  • cosmosdb

  • databricks

  • db2

  • db2i

  • db2z

  • derby

  • dynamodb

  • edb

  • firebird

  • hana

  • h2

  • hsqldb

  • informix

  • ingres

  • mariadb

  • maxdb

  • mongodb

  • mssql

  • mysql

  • neo4j

  • oracle

  • postgresql

  • redshift

  • snowflake

  • sqlite

  • sybase

  • teradata

  • vertica

  • yugabytedb

Separate multiple values with commas. Specify that a changeset does not apply to a particular database type by prefixing it with ! The default value is all.

Uses

If you're deploying a changelog to multiple database management systems (DBMSs), you may want to ensure that a specific changeset is only deployed to one type of database. For example, you might want to deploy some stored logic only to your PostgreSQL databases because the logic uses a keyword that doesn't exist on your Oracle databases. You can specify

Note: Liquibase dynamically uses the database connection URL to determine what database you're currently connected to, not the value of dbms.

Syntax

--liquibase formatted sql --changeset your.name:1 dbms:postgresql,oracle create table person ( name varchar(255) );