The latest version of Liquibase has a pre-installed driver for this database in the $LIQUIBASE_HOME/internal/lib directory, so you don't need to install it yourself.

If you prefer, you can use environment variables to point to the directory where Liquibase is installed on your machine. You can set environment variables using your operating system's shell. The location of $LIQUIBASE_HOME will depend on where Liquibase was installed on your machine.

Note for Maven users: If you're running Liquibase using the Maven plugin using mvn liquibase:update, installing the extension with Maven ensures the right files are available and everything works together automatically. You can manage these extensions by adding them as dependencies in your project’s pom.xml file. Configuring Maven this way ensures that the necessary JAR files are retrieved from Maven Central during the build phase.

To validate that Snowflake is available, you can use the SnowSQL CLI tool and run connect. You can also log into the Snowflake console in your browser to validate that the instance is running. The browser link is different for each Snowflake instance, but the format is:

https://<cloudHostName>.snowflakecomputing.com

You will receive an email with the link when the database is ready for use.

Grant schema permissions for all SQL statements you intend to use in your Liquibase changelogs, such as CREATE TABLE if you want to create a new table.

Specify the database URL in the liquibase.properties file (defaults file), along with other properties you want to set a default value for.

Liquibase does not parse the URL. You can either specify the full database connection string or specify the URL using your database's standard connection format: url:

jdbc:snowflake://<account_ID>.snowflakecomputing.com/?<connection_params>

Note: The account ID is the host name for your Snowflake instance. Snowflake sends an email with the URL to the host. The JDBC driver only needs the hostname, not the full URL: tn12345.us-east-1.snowflakecomputing.com.

Example: Depending on the cloud provider you select during the database creation, your domain name will be different. The example is for an AWS cloud instance: jdbc:snowflake://tn12345.us-east-1.snowflakecomputing.com/?db=lbcat&schema=public.

Tip: To apply a Liquibase Pro key to your project, add the following property to the Liquibase properties file: licenseKey: <paste code here>

(Optional) If you're using PKI or OAuth to connect to Snowflake instead of the traditional username and password method, refer to the Authenticate with Snowflake PKI or OAuth article to set up authentication.

1. Create a text file called changelog (.sql, .yaml, .json, or .xml) in your project directory and add a changeset.

If you already created a changelog using the init project command, you can use that instead of creating a new file. When adding onto an existing changelog, be sure to only add the changeset and to not duplicate the changelog header.

2. Navigate to your project folder in the CLI and run the Liquibase status command to see whether the connection is successful:

liquibase status --username=test --password=test --changelog-file=<changelog.xml>

Note: You can specify arguments in the CLI or keep them in the Liquibase properties file.

If your connection is successful, you'll see a message like this:

4 changesets have not been applied to <your_connection_url> Liquibase command 'status' was executed successfully.

3. Inspect the deployment SQL with the update-sql command

liquibase update-sql --changelog-file=<changelog.xml>

If the SQL that Liquibase generates isn't what you expect, you should review your changelog file and make any necessary adjustments.

4. Then execute these changes to your database with the update command:

liquibase update --changelog-file=<changelog.xml>

If your update is successful, Liquibase runs each changeset and displays a summary message ending with:

Liquibase: Update has been successful. Liquibase command 'update' was executed successfully.

5. From a database UI tool, ensure that your database contains the test_table object you added along with the DATABASECHANGELOG table and DATABASECHANGELOGLOCK table.