Lone Badger Tech

How it compares

Flyway, DbUp, grate, EF Core migrations, SSDT, Sqitch and Liquibase.

Every tool here is good at something. This is how Badger SQL Migrate's design relates to them, for SQL Server, Azure SQL and PostgreSQL. Feature sets change; check each project for its current state.

Badger SQL MigrateFlywayDbUpgrateEF CoreSSDT / dacpacSqitchLiquibase
Free down / undoYesPaidNoNoYes (generated)Partly (older dacpac)YesYes (targeted: Pro)
Two developers adding changes at onceYes (named + union merge)No (same V number)PartlyPartlyPartly (snapshot conflicts)YesPartly (plan conflicts)Partly (changelog conflicts)
Cryptographic hash of every changeYes SHA-256Partly CRC32NoYesNoNoYes SHA-1Partly MD5
Certifies the order across machinesYes hash chainNoNoNoNoNoYesNo
Same SQL on every machineYesYesYesYesYesNo (diff at deploy time)YesYes
Rollback without the original checkoutYes (stored in DB)NoNoNoNoNoNoNo
Explicit dependencies between changesYesNoNoNoNon/aYesNo
Schema drift detectionYesPartly (paid)NoNoNoYesNoPartly (Pro)
Deploy lock for concurrent pipelinesYesYesNoPartlyYes (EF 9+)NoYesYes
Per-environment config and protectionYesYesNoPartlyNoPartlyYesYes
Every Entra ID flow incl. MFAYesPartlyPartlyPartlyPartlyPartlyNoPartly
Always Encrypted key provisioningYesNoNoNoNoPartlyNoNo
Repeatable scripts (views, procs)YesYesNoYesNoYesNoYes
No runtime to installYes single binaryNo JVMlibrary.NET tool.NETSqlPackageNo PerlNo JVM

What Badger SQL Migrate keeps

What it fixes

Coming from another tool? See Existing databases for adopting a database that is already in production.