sqlx-cli

sqlx-cli is a command-line tool for database setup, SQL migrations and SQLx query-macro workflows. It is best suited to Rust teams already using SQLx and a supported database. Its appeal is a free, focused toolkit that can also check query metadata in CI; it is not the right fit for MSSQL projects.

Overview

SQLx is an asynchronous, pure-Rust SQL toolkit with compile-time checked queries, and sqlx-cli brings several related database tasks into the command line. It can create or drop the database named in your connection configuration, manage migrations and prepare metadata for query macros. The CLI is open source under either Apache-2.0 or MIT, at the user's option.

Commands require a database URL, supplied with --database-url, through the DATABASE_URL environment variable, or in a .env file in the current working directory. That keeps configuration flexible, but also makes connection setup a necessary part of local and CI workflows.

Key features

Database and migration management

The CLI can create and drop the configured database, and create, run, inspect or revert migrations. Paired up and down SQL scripts provide a direct way to define changes and reversals. This is a sensible fit for SQLx projects that want routine database and migration work in one Rust-oriented tool. Teams seeking a migration workflow outside SQLx may find a dedicated alternative a better match.

Offline query metadata and CI

cargo sqlx prepare saves query metadata in a .sqlx directory. Once that directory is checked into version control, builds can proceed without an active database connection. For a workspace with multiple crates using query macros, cargo sqlx prepare --workspace places a single metadata directory at the workspace root.

For CI, cargo sqlx prepare --check returns a nonzero status when saved metadata is out of date, making stale query metadata visible in an automated check. Setting SQLX_OFFLINE=true forces offline builds even if a database URL or .env file is present. These features reduce the need for a live database during builds, though teams still need to prepare and maintain the checked-in metadata.

Drivers and connection options

The project lists PostgreSQL, MySQL, MariaDB and SQLite as supported databases. Installation is documented through cargo install sqlx-cli, with feature options to select database drivers and TLS backends, including native TLS, vendored OpenSSL and Rustls. Choosing features makes the installation more configurable, but requires matching the build to the project's database and connection needs.

For non-TLS MySQL or MariaDB connections where the server requires RSA authentication using caching_sha2_password or sha256_password, the mysql-rsa feature is needed. MSSQL support was removed pending a full rewrite of the driver as part of the SQLx Pro initiative, so SQL Server users should choose another tool.

Pricing

sqlx-cli costs nothing. The free plan includes database management, migrations and offline query metadata; there is no free trial because the software is free to use. The open-source project offers a choice of Apache-2.0 or MIT licensing. That makes it a straightforward option for SQLx projects that need these command-line workflows without a paid plan.

Platforms

sqlx-cli supports Linux, macOS and Windows. Its database coverage and TLS configuration depend on the driver and backend features selected during installation.

Who it's for

Choose sqlx-cli if your project uses SQLx with PostgreSQL, MySQL, MariaDB or SQLite and you want database lifecycle commands, SQL migration management and query-macro metadata preparation together. Its offline build support and metadata check are especially useful for teams that want query changes checked in CI. Look elsewhere if you need MSSQL support or do not want to manage database URL configuration.

Pros and cons

• Pros: A free, open-source CLI combines database creation and removal with migration creation, execution, inspection and reversion.
• Pros: Checked-in query metadata enables offline builds, and --check can flag stale metadata in CI.
• Pros: Driver and TLS feature choices let installations target different database and connection setups.
• Cons: Commands require a database URL, so local and automated environments need deliberate connection configuration.
• Cons: MSSQL support has been removed, ruling out SQL Server projects.
• Cons: Some non-TLS MySQL or MariaDB setups require the additional mysql-rsa feature.

Alternatives

If you want to compare migration-focused tools, start with Database Migration Tools. Skeema has a free Community plan with tables, stored procedures and functions, and 18 linter checks; it may suit teams looking for those schema and linting capabilities. Its Plus plan costs $124 a month.

Sqitch is another free database change-management application, with a license permitting use, modification and distribution. Atlas is an open-core alternative with an Apache-2.0 core, advanced features and a free trial.

dbmate is a free open-source migration tool with no paid SaaS upsell stated, while FluentMigrator is an Apache-2.0 licensed framework distributed through NuGet, with provider packages selected separately. Goose is a free open-source migration tool.

pgroll is a free option for PostgreSQL 14.0 or later, distributed as a single cross-platform binary. Refinery is a free MIT-licensed SQL migration toolkit whose database drivers must be selected as features.

Verdict

sqlx-cli is a strong choice for Rust developers already building with SQLx who want migration commands and offline query-macro preparation in the same free tool. Its CI metadata check is a practical advantage for keeping query metadata current. Choose another option if your project needs MSSQL support or a workflow that does not depend on SQLx and database URL configuration.