Skip to content

Sql2DevOps

Sql2DevOps runs SQL packages (DDL, functions, procedures, data) against your databases, records every execution in a Git repository you own and promotes each package from development to production under the approval rules you choose, with a tracked emergency path for when the rules must be bypassed.

It is one small executable for Windows, Linux and macOS. There is no server to install, and nothing is ever sent to us.

What it solves

Problem How Sql2DevOps handles it
Production runs something different from what was tested A package is submitted once as an immutable, hashed copy; every environment runs that copy, and only after the same version succeeded in the previous one
Nobody knows what ran where A signed, hash-chained history in Git, plus a sql2devops_history table in each database; status shows every package in every environment
A database was restored from a backup, or a script was run by hand Both records are compared before each deployment; manual runs can be recorded
A script fails halfway Steps with rollbacks run in reverse order; the report gives the exact line, the server's error and the database's state
Emergencies skip every rule and leave no trace emergency requires a reason, is recorded, and leaves a review and the skipped environments as follow-ups
Tooling friction One static executable, no drivers or database clients to install

How it fits together

 your scripts ──► package (folder + sql2devops.yaml)
                       │ package submit
                       ▼
            control repository (Git): immutable copy, signed history
                       │ promote / deploy
                       ▼
        DEV ──► HML ──► PROD      each database keeps sql2devops_history
             approvals per environment, emergencies with follow-ups

Where to go next

  • Getting started: install and run your first package in a few minutes.
  • Concepts: packages, the control repository, environments and approvals.
  • Pipelines: GitHub Actions, GitLab CI, Azure DevOps and Jenkins.
  • Commands: every command and option.

Prefer reading offline?

The whole documentation is also available as a PDF.