Database Change AutomationRequested. Reviewed. Deployed. Audited.
Database changes run through a workflow — request, review, deployment, audit. The 6 levels show how teams get there, and where most plateau.
Database automation maturity
Six levels. From manual to integrated.
Borrowed from the levels of autonomous driving. Each level removes a class of manual work and exposes the next bottleneck.
- L0
No automation
Direct DB clients. Every change typed and run by hand.
- L1
Ticketing
Jira or ServiceNow captures the request, approval, and audit trail. SQL is still executed by a human.
- L2
Version controlled
Schema history and change scripts live in Git. Deployment is still manual.
- L3
Streamlined
Liquibase, Flyway, or sqitch run inside CI/CD. Deployment automated, cross-tool stitching still manual.
- L4
Integrated
Change, ad-hoc access, and audit in one platform. The current ceiling in production.
- L5
Fully automated
End-to-end including self-healing. Aspirational.
The basics
Know the territory.
- 01
Map the levels
The 6 levels of database automation, from L0 manual SQL to L5 self-healing. Where teams plateau, and what each level removes.
- 02
Define the discipline
What DCM is, why it's hard, and why DDL, DML, and DCL belong in one workflow.
- 03
Know the gates
What a Change Advisory Board is, where it slows teams down, and how it coexists with automated pipelines.
The three approaches
Three approaches. One outcome.
Ticketing-led
Jira, ServiceNow, or a homegrown queue. Captures the request and the approval — the SQL runs somewhere else.
Read →Pipeline-led
Migration scripts in Git, CI runs lint and review, deployment runs in the same pipeline as the application.
Read →Platform-led
One tool replaces the bastion / ITSM / PAM stack. Approval, credential, and execution share the same record.
Read →
Database automation in Bytebase
Change, access, and audit in one workflow.
Schema changes run as pull requests. SQL review, lint, and policy checks run before execution. Ad-hoc access flows through the same approvals. Every action — change, query, export — lands in one audit log. ServiceNow and Jira plug in for CAB approvals. GitHub, GitLab, Bitbucket, and Azure DevOps plug in for execution.
One platform. Every change.
Database automation questions
Common questions.
- What does it mean to automate database change?
- Automating database change means request, review, deployment, and audit run as one structured workflow — not as ad-hoc tickets, chat messages, and SQL clients. Hand-off points are recorded. Humans gate risk; the system executes.
- Where do most teams plateau on the automation curve?
- Most teams plateau at Level 3 — schema in Git, migrations applied by Liquibase or Flyway through CI/CD. Change is automated; ad-hoc access, audit, and policy enforcement still live in separate tools. Level 4 consolidates them into one workflow.
- Can we keep using ServiceNow or Jira and still automate?
- Yes — and most enterprises do. ServiceNow or Jira owns the change request and CAB approval. An automation layer (CI/CD pipeline or change-management platform) owns execution, policy checks, and the audit record. Webhooks or APIs link the two so the ticket reflects what ran.
Every post in the series.
Definitions
- 01
The 6 Levels of Database Automation
Six levels borrowed from autonomous driving. L0 to L5, and where teams plateau.
- 02
What is Database Change Management (DCM)?
Definition, why it's hard, the workflow it requires, and how it fits into DevOps.
- 03
What is a Change Advisory Board (CAB)?
What a CAB is, where it slows teams down, and how it coexists with automated pipelines.
The three approaches
- 04
Hope Is Not a Strategy: Why Jira Falls Short for Database Change
What a custom Jira workflow for database change looks like — and where it breaks at scale.
- 05
How to Build a CI/CD Pipeline for Database Schema Migration
What the pipeline gates, what it leaves outside, and the tools that fit.
- 06
Securing Database Change: From Bastion to Integrated Platforms
The bastion / ITSM / PAM stack teams build around DB change, and what an integrated platform replaces.