BroadSQLWhy BroadSQL?
Graphical tools are excellent for database design or one-off exploratory queries. But when your daily routine involves managing data across multiple servers, vendors, and environments, a point-and-click session doesn't preserve your work.
A command-line client earns its place when you need repeatability, speed, and automation.
Going Beyond the Baseline
Most SQL clients—whether command-line or graphical—are judged on five core capabilities: connecting, browsing, querying, extracting, and automating. BroadSQL meets the industry baseline on every one of them, but pushes far beyond typical market expectations in export flexibility, automation, and extensibility.
| Expectation | Typical SQL Client | BroadSQL |
|---|---|---|
| Connect & Browse | Connections tree, schema browser, query editor | Named connections, SHOW TABLES, DESCR, FIND COLUMN, and plain SQL passthrough |
| Export Results | One destination format per run via a GUI wizard | PULL: One syntax for all formats (H2, Excel, CSV, JSON, Markdown, HTML) |
| Automate Work | Often restricted to a paid tier or missing entirely | Script files, saved query library, and per-connection login scripts—all in the free product |
| Extensibility | Heavy plugin SDKs (IDE APIs) or strictly closed | Drop a plain .jar in /extensions. No rebuilds, no complex SDKs. |
(See our Compare page for a tool-by-tool breakdown against usql, DBeaver, and DataGrip).
1. The same query, every environment
Connections in BroadSQL are named, not hard-coded into a saved workbook. Need to switch from DEV to TEST to PRODUCTION? Or migrate between completely different database vendors? You just change the connection name, not the query.
Using the / command instantly re-runs your last query as-is against whichever connection is currently active. A query validated on TEST can be executed on PROD in seconds without retyping a single character.
2. Exports and imports are one command away
Moving data shouldn't require clicking through a five-step wizard every time.
PULLcopies a query's results directly into a local H2 database, a spreadsheet tab, or a structured file (CSV, JSON, Markdown, HTML) using the exact same syntax for every destination.EXPORT/DUMPwrites full queries or entire tables to Excel, OpenDocument Spreadsheet, CSV, or plain text.LOADsafely ingests CSV files back into a table, complete with built-in validation, a safety preview, and explicit authorization.
3. Scripts, not click-paths
A BroadSQL script file lets you freely mix standard SQL with native BroadSQL commands, running seamlessly against any connected database type—something a vendor-specific GUI client simply cannot do. By combining script files, the saved query library, and file macros (like @file.sql or <@codes.txt>), you can turn a tedious recurring task into a single command you run once and reuse forever.
4. Extend it yourself (without the wait)
Most SQL clients force you to build against their host IDE's heavy plugin platform (like an Eclipse/OSGi plugin for DBeaver, or an IntelliJ plugin for DataGrip), requiring you to learn a new build toolchain before writing a single line of code. Command-line alternatives often offer no extension mechanism at all.
BroadSQL makes extending your toolset as easy as writing a small standalone program. Just drop a plain JAR file into the extensions/ folder. Your extension gets direct access to the console, the active connection, and the command interpreter.
This matters most for organization-specific workflows a generic SQL client will never ship: a custom schema naming-convention linter, a one-command reconciliation check against an internal API, or a shortcut for a complex query pattern your team runs every week. Instead of filing a feature request and waiting months, write it once, drop it in, and it behaves exactly like a native BroadSQL command.
Built for Production Work
- Works out of the box: Ships with native support for H2, PostgreSQL, Apache Derby, HSQLDB, and SQLite. Connect to any other JDBC-compatible database simply by adding its driver (see technical requirements).
- Secure by design: Your connection URLs and passwords are never stored in plain text. They live in an AES-encrypted local database (the CDF), unlocked by a single master password.
Ready to see it for yourself? Get started or download the latest release.