The file has to be there every morning

DBToFile » Use cases » Export on a schedule

Download DBToFile Free Trial »     Buy DBToFile Now »

The situation

Something downstream reads a file, not a database: a report in a spreadsheet, a BI import, an upload to another system, or a colleague who opens the same CSV every morning. The data is in a table, and it changes during the day.

Somebody has to export it again, every day, at the right time - and that "somebody" is the reason the file is occasionally a day old.

What you do

  1. Set the export up once: open the table, choose the output format (CSV, Excel, JSON, XML, HTML, SQL, TXT/TSV), pick the destination folder and file name.
  2. Click Save Session so the whole configuration is stored.
  3. Run the session from the command line and give that command to Windows Task Scheduler, cron, or your pipeline.
  4. Run it once by hand and open the file, to be sure the format is what the reader expects.

A DBToFile export run, showing progress and the log

The same session exports the same table the same way every time, and the file is overwritten in place, so the reader never has to look for a new name. Windows, Linux and macOS are all supported, and the export runs on the machine that holds the credentials - nothing is uploaded to a cloud service.

What it will not do

Related

Doing it headless: command line, saved setup: sessions. The export itself: table to file, query to file, many tables at once. Formats and databases: supported conversions. Not sure the file will fit: more rows than Excel can hold.