Database CI/CD
Database CI/CD Pipeline Automation: Glossary & Technical Reference
A reference glossary of key terms and acronyms used in database CI/CD pipeline automation, covering migrations, deployment patterns, and the tooling that orchestrates schema change delivery.
A
Automated Testing
Programmatic validation of schema changes before deployment: Does the change cause syntax errors? Does it break application queries? Does it degrade performance on production-scale data?
Automation Framework
Tool or platform that orchestrates database CI/CD pipelines: Liquibase, Flyway, Atlas, CloudSQL, AWS DMS, etc.
B
Baseline Schema
The initial, version-controlled state of a database schema. Used as the starting point for all subsequent migrations.
Blue-Green Deployment
Pattern where two identical production environments (blue and green) exist. Deploy to green while blue serves traffic, then switch traffic to green. Allows instant rollback by switching back to blue.
Backwards Compatibility
Property of a schema change that doesn't break existing applications or queries. A schema change is backwards compatible if applications built for the old schema continue working.
C
Changeset
Atomic unit of database change (typically one migration script). A changeset represents a single logical change (add table, create index, etc.).
Continuous Deployment
Automatically deploying database changes to production after passing tests, without requiring manual approval. Requires high confidence in automated testing.
Continuous Integration
Automatically running tests on schema changes every time code is committed, catching errors early.
D
Data Migration
Movement of existing data to accommodate schema changes. Distinguished from schema migration: changing the structure vs. moving/transforming the data.
Declarative Migration
Approach where you define desired final schema state; the tool determines required migrations. Contrast with imperative.
Database State
The current configuration of a database: what tables exist, what columns they contain, what indexes exist, etc.
Downtime Window
Planned period during which database is unavailable for schema changes that cannot be executed online.
E
Environment Parity
Similarity between environments (dev, staging, production). Testing schema changes in staging with production-like data volume and structure provides parity.
I
Imperative Migration
Approach where you write explicit SQL statements defining each migration step. The developer controls exactly what SQL executes.
Index Management
Creating, modifying, and dropping indexes as part of schema migrations. Index changes have performance implications and must be tested.
M
Migration Script
Version-controlled SQL or code file defining a schema change. Each migration is numbered/timestamped and executed in strict order.
Migration Tool
Software that manages database migrations: Flyway, Liquibase, Alembic, Atlas. Handles versioning, execution, rollback, and audit trails.
Migration Version
Unique identifier for a migration (typically timestamp or sequence number) ensuring migrations execute in correct order.
R
Rollback
Reversion of a schema change. Automatic rollback means the system executes reverse migrations without human intervention when deployment fails.
Reverse Migration
Migration script that undoes a previous change. If forward migration adds a column, reverse migration drops it.
S
Schema Change
Alteration to database structure: adding/dropping tables, columns, indexes, constraints, etc.
Schema Drift
Divergence between expected schema (from version control) and actual schema in database. Caused by manual changes or failed migrations.
Schema Registry
Centralized repository tracking what schema exists in each environment, used to detect drift and coordinate deployments.
Schema Versioning
Numbering/timestamping schema versions so changes can be tracked, applied, and reverted in consistent order.
Staging Environment
Pre-production environment (ideally with production-like data) where schema changes are tested before deploying to production.
State-Based Migration
Tool compares desired schema state to current state and generates required migrations. Contrast with migration-based.
T
Test Automation
Automated validation of schema changes: correctness tests, performance regression tests, compatibility tests.
Transaction
Atomic unit of database work. Migrations are typically wrapped in transactions so they either fully succeed or fully roll back.
V
Version Control
System (Git, etc.) tracking changes to migration scripts over time, who made changes, when, and why (via commit messages).
Versioning Scheme
Strategy for numbering migrations: sequential (001, 002, 003), timestamp-based (20240115_120000), or semantic.
Key Acronyms
| Acronym | Meaning |
| CI/CD | Continuous Integration / Continuous Deployment |
| DBA | Database Administrator |
| SQL | Structured Query Language |
| ETL | Extract, Transform, Load |
| ORM | Object-Relational Mapping |
| DDL | Data Definition Language (schema changes) |
| DML | Data Manipulation Language (data changes) |
See Database CI/CD in 4DAlert
Explore how 4DAlert implements the concepts in this guide as a working platform.