A nightly SQL extract on an SFTP server, every night.
DataBridge runs a saved query on a schedule and delivers the result to an SFTP server as CSV, TSV or JSON, with a record of every run.
Someone else needs yesterday's orders, receipts or balances as a file on an SFTP server. A script on a scheduled task works until the day it fails quietly and nobody knows.
Modules. Everything bundle: Database to read, Transfer to deliver, Flow to schedule.
Edition. DataBridge Server for unattended schedules.
How DataBridge does it.
Each step names the feature as it appears in the product.
- Step 1
Database connection
Connect to SQL Server, PostgreSQL, MySQL or SQLite with a login that can only read. Test shows the server version before you save.
- Step 2
Saved query
Write the SELECT once, with @parameters if you need them. Only read-only statements are accepted.
- Step 3
Destination
Add the SFTP server. Test reports the server's host key fingerprint; pin it, and DataBridge refuses any other server at that address.
- Step 4
Scheduled job
Execute query, then Push results, with a file name pattern such as {date}. Set a daily time and the server's time zone, and retry on failure.
- Step 5
Send once
For feeds such as new invoices, Send once remembers what was delivered, so each row goes out one time.
- Step 6
Job Monitor
Every run lists its steps, rows, duration and delivered file. A failure can email you.
What this does not do.
- The SFTP destination form takes a password. Key-only SFTP servers need the API route for the private key today.
- A job carries a limited number of rows (the Pull:MaxRows setting), and a Send once step fails rather than guess when the result is over it.
- Failure emails need the server's email set up. Without it, alerts go to the log only.
Related pages.
Try the parts that are free today.
The free browser edition needs no sign-in and never uploads your files.