Articles

Practical write-ups on using BroadSQL for specific, recurring jobs.

Run the same SQL query across multiple databases and environments

When you manage DEV, TEST, and PROD, or Postgres, Oracle, and SQL Server side by side, the query stays the same but the tool changes every time.

Export SQL query results to Excel or CSV from the command line

Getting query results into Excel usually means a GUI, some copy-pasting, or a different one-off script for every output format.

Compare and reconcile data between two databases or environments

After a migration, a sync, or a release, you need to prove PROD still matches the source: row counts, checksums, key differences, often across different vendors.

Automate recurring SQL tasks to run unattended

Scheduled extracts, health checks, and data loads are the same steps every night: done by hand, or scattered across brittle, per-environment scripts.

Build a diagnostic query library for support teams

When an incident spans environments, engineers end up rewriting the same investigative queries from memory: differently each time, often with production credentials in plain sight.

Store and manage database credentials securely across many connections

Working across dozens of databases usually means passwords living in scripts, config files, or sticky notes, and that's an audit finding waiting to happen.

Cross-vendor SQL on Windows without a GUI

A single command-line SQL client that reaches Oracle, SQL Server, Postgres, and more on Windows, with every driver behaving identically and no build step, is surprisingly rare.