Sqitch vs SQLancer

Sqitch is a database change management application for deploying and tracking database changes. It is a standalone system, not tied to a framework, ORM, database engine, or development environment. Changes are written as scripts native to the chosen database, and can declare dependencies—including changes in other Sqitch projects—to establish execution order. A plan file and Merkle tree pattern support deployment integrity without requiring numbered change names. Sqitch can deploy and revert changes, report status and history, and run optional verification scripts. Its manual lists PostgreSQL, YugabyteDB, CockroachDB, SQLite, MySQL, MariaDB, Oracle, Firebird, Vertica, Exasol, Snowflake, and ClickHouse. Connecting and executing scripts requires the database's native command-line client and connector libraries. Installation options include source, Docker, Linux distribution packages, macOS Homebrew, and Windows instructions. Sqitch is free, with a license permitting use and distribution, and is available for Linux, macOS, Windows, and self-hosted use.

SQLancer automatically tests database management systems to find implementation bugs. It generates SQL statements and database states, then validates query behavior with test oracles including TLP, NoREC, PQS, DQP, CODDTest, and CERT. Targets include logic bugs, performance issues, unexpected internal errors, and crashes. The supported-databases list contains 21 implementations, including PostgreSQL, MySQL, SQLite, DuckDB, and ClickHouse, while the impact page reports evidence of use by 22 DBMS projects. SQLancer runs on Linux, macOS, and Windows and requires Java 11 or above plus Maven. Releases are available through GitHub, Maven Central, and DockerHub. DuckDB, H2, and SQLite can run as embedded systems with binaries included as JAR dependencies. Runs may continue indefinitely when no bugs appear, with options to stop after a selected bug count or timeout. It is free under the MIT License.