Skip to main content

Database DevOps (DB DevOps) FAQs

Last updated on

This page answers common questions about Harness Database DevOps (DB DevOps) and how it integrates database changes into modern CI/CD workflows.

What is Harness DB DevOps?​

Harness Database DevOps (DB DevOps) is a module that enables teams to manage database changes using the same CI/CD practices used for application code.

It integrates database schema changes into deployment pipelines, providing visibility, governance, and automation for database deployments across environments.

Key capabilities include:

  • Pipeline-driven database deployments
  • Version-controlled database changes
  • Integration with application CI/CD workflows
  • Governance and approval workflows
  • Auditability and deployment visibility

This approach allows teams to manage database code alongside application code, improving reliability and consistency across environments.

Which database migration tools are supported?​

Harness DB DevOps supports popular database migration frameworks including:

  • Liquibase
  • Flyway

Organizations can continue using their preferred migration tool while leveraging Harness pipelines to orchestrate and manage database deployments.

The migration framework executes the schema changes, while Harness provides:

  • pipeline orchestration
  • deployment visibility
  • governance and approvals
  • integration with CI/CD workflows

Does DB DevOps support rollbacks?​

Yes. Harness DB DevOps supports rollbacks through a dedicated pipeline step that safely reverts previously applied database changes. The Apply Rollback step allows teams to revert database changes executed during earlier deployments while maintaining visibility and control within the pipeline workflow.

Learn more about rollbacks in the DB DevOps documentation.

How does DB DevOps manage database changes with application deployments?​

Database and application changes can be orchestrated within the same Harness pipeline to ensure coordinated deployments. This allows teams to:

  • deploy database schema changes before application releases
  • validate database updates during pipeline execution
  • maintain consistency across environments

Application deployments require a Harness Continuous Delivery (CD) license. However, database deployments can still be managed independently within Harness pipelines.

Can DB DevOps be used independently of Harness CD?​

Yes. Database deployments can be executed through Harness pipelines without deploying application services. However, if you want to deploy applications and databases together in the same pipeline, a Harness CD license is required.

How are database changes tracked and audited?​

Database changes are tracked through both the migration framework and Harness platform capabilities.

Typically:

  • migration scripts or changelogs are stored in source control
  • migration tools track applied changes using metadata tables
  • Harness pipelines record deployment history and execution logs

This provides a complete audit trail of:

  • what changes were deployed?
  • when deployments occurred?
  • which environments were affected?

What databases are supported?​

Harness DB DevOps supports databases that are compatible with the underlying migration frameworks (Liquibase or Flyway).

Commonly used databases include:

  • PostgreSQL
  • MySQL
  • Oracle
  • SQL Server
  • CockroachDB
  • MongoDB
  • Amazon RDS
  • MSSQL Azure
  • Google Cloud SQL
  • Snowflake
  • AlloyDB

Support ultimately depends on the compatibility of the migration framework being used.

How does DB DevOps help prevent unsafe database changes?​

Harness DB DevOps helps teams reduce deployment risk through governance and pipeline controls.

Examples include:

  • Approval gates before production deployments
  • Pipeline validation steps
  • Environment-based deployment controls
  • Audit logging and deployment visibility

These capabilities help teams introduce controlled, repeatable database deployment processes across environments.

Can Harness Database DevOps be used to migrate databases from Azure SQL to Google Cloud SQL (or across any cloud providers)?​

Partially. Harness Database DevOps is an orchestration layer, not a data migration or replication tool. It does not move data between databases or cloud providers.

For a cross-cloud database move (for example, Azure SQL to Google Cloud SQL), you need two separate tools working together:

  • Data transfer tool: Use a dedicated service such as Azure Database Migration Service, pg_dump/pg_restore, or a cloud-native replication tool to copy the existing data to the target database.
  • Harness DB DevOps: Once the target database exists, Harness orchestrates the schema migration portion. It applies your Liquibase or Flyway changelogs to the target, manages approval gates, sequences the rollout across environments, and records the full deployment audit trail.

Harness connects to any database reachable from your network through the Harness Delegate. You configure a database connector pointing at the target (Google Cloud SQL in this example), and Harness runs the migration pipeline against it exactly as it would in any other environment.

In short, use your cloud provider's data migration service to transfer data, and use Harness to deploy and govern the schema on the new database.

Last updated on