Automate recurring SQL tasks to run unattended

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

The problem: operational work that repeats, without a home of its own

Most operational SQL work is repetitive by nature: the same nightly extract, the same health check, the same load into a reporting table. It usually ends up as a collection of scripts written at different times, by different people, each one hard-coding a connection or a password, none of them easy to hand to someone else.

The BroadSQL approach: one script file, run unattended, retargeted by name

A BroadSQL script file mixes plain SQL and BroadSQL's own commands freely, and runs the same way against any connected database:

-- nightly_extract.sql
CONNECT prod_reporting;
PULL (SELECT * FROM orders WHERE order_date = CURRENT_DATE - 1) TO daily.orders AS CSV;
BATCHLOAD UPDATE customer_status c:\imports\status_updates.txt;

@c:\scripts\nightly_extract.sql;

The whole file runs unattended from a single @ command, kicked off by cron or Windows Task Scheduler like any other command-line job. Re-targeting it to a different environment is a one-word change (the connection name in the CONNECT line), not a rewrite, and the script itself is a plain text file that belongs in version control like any other piece of infrastructure.

Honest scope

BroadSQL doesn't include its own scheduler, retry logic, or alerting. It expects your OS's own scheduler (or a proper job orchestrator, for anything more demanding) to trigger it, and it reports success or failure the way any command-line tool does. What it removes is the need for a custom-written client or a fragile wrapper script just to talk to the database.

Who this is for

Service delivery and ops teams running the same operational SQL work every night, across more than one environment, who want that work in version control instead of scattered across individual scripts.

Get your recurring work automated

I set up automation like this end to end: the script files, the scheduling, and a support retainer if you want someone to own it going forward, rather than it living on one person's laptop. Get in touch to talk about what runs on your side every night.