Run SQL. Runs a custom SQL statement against the configured database without returning any rows, typically to update or clean up data.
Export SQL result to file. Runs the configured SQL query and writes the result to a file (CSV, fixed-width or XML) using the export format options of the step.
The action runs as a step in a SyncTool configuration. You configure the step's settings (e.g. server, login, path, format or SQL depending on the action) and run the configuration. The action fetches the data it needs from Sapera or the external source itself – you do not map source columns as you would for a regular import.
Run SQL executes your SQL statement against the configured database without returning rows – typically to update or clean up data. Export SQL result to file runs the query and writes the result to a file (CSV, fixed width or XML) according to the step's export format.
Often combined with e.g. an FTP or e-mail step that sends the generated file on.
An export whose query uses a 'since last run' time window supports two optional fields on the step: Re-run from date and Re-run to date. Fill in both (e.g. 2026-06-01 and 2026-06-30) to produce one file per day in the range, each with that day's date in the file name if the name contains @currentExecutionDate. The fields are temporary only: the value is never saved to the .ssd file, and a re-run does not change the step's normal 'since last run' timestamp, so the daily run continues undisturbed. Leave the fields empty for normal operation.
See also the overview SyncTool – actions.
Want to know more?
Read more in these related articles:
Standard parameters for all actions
The general parameters available on most SyncTool actions: step control, error handling, timeout, etc.
