BATCHLOAD

Loads records from a CSV file into a table using batches of queries.

Arguments

BATCHLOAD <updateMode> <tableName> <fileName> where: <updateMode> is CREATE or UPDATE <tableName> is a valid table name <fileName> is a valid file name

Examples

BATCHLOAD CREATE customer c:\temp\queries.txt
LOAD UPDATE customer c:\temp\queries.txt

Notes

Bulk-loads a semicolon-separated CSV file into a table as a single batched transaction: BATCHLOAD <CREATE|UPDATE> <tableName> <fileName>. All three arguments are mandatory.

The file's first line must be a header naming real columns of tableName; columns can be listed in any order and only the ones you need have to be present. In CREATE mode, every header column is inserted. In UPDATE mode, the <em>first</em> header column is the key used to locate the row (it is not itself updated) and the remaining columns are set. Each value is converted to the target column's real type (numeric, boolean, text, or dd-MMM-yy dates, plus the literal sysdate); a value that doesn't convert is stored as NULL rather than aborting the row. If fileName has no path, it is resolved inside the configured export folder (DefaultFolder in BroadSQL.ini).

A row whose insert/update fails is skipped (logged) and the rest of the file still runs. A <fileName-without-extension>_LOG.txt file is always written next to the source file with one entry per row, and the console reports how many rows were attempted versus actually inserted/updated. Unlike LOAD, this command does not check that tableName exists before starting.

Last modified in release 4.9.8.