Overview
The Bulk Load Builder is a guided UI for the Bulk Load SQL field in ETL flows with bulk load and the Bulk load files into the database flow. Instead of memorizing directive or SQL syntax, you pick a load method, fill in its options, and the Builder generates the value into the field.
Available in Etlworks 9.9.8 and later.
Open the Builder
1. On the transformation, open MAPPING → Parameters and click into the Bulk Load SQL field to open the code editor.
2. Click Build bulk load in the editor toolbar.
The Bulk Load Builder dialog opens
Available methods
The Builder offers client-side providers and classic database-executed SQL templates:
| Method | Kind | Generates |
|---|---|---|
| SQL Server Bulk Copy | Client-side | SQLSERVER_BULK_COPY WITH (...) |
| PostgreSQL Copy | Client-side | POSTGRES_COPY WITH (...) |
| MySQL Load Data Local | Client-side | MYSQL_LOAD_DATA_LOCAL WITH (...) |
| SQL Server BULK INSERT | Database-executed SQL | BULK INSERT {TABLE} FROM ... template |
| PostgreSQL server-side COPY | Database-executed SQL | COPY {TABLE} FROM ... template |
| MySQL server-side LOAD DATA INFILE | Database-executed SQL | LOAD DATA INFILE ... template |
| Vertica COPY FROM LOCAL | Database-executed SQL | COPY {TABLE} FROM LOCAL ... template |
Read about the client-side providers, their options, and prerequisites in Client-side bulk load into SQL Server, PostgreSQL, and MySQL.
Compatibility detection
The Builder reads the flow's destination connection, staging connection, and staging format, then:
- recommends the client-side methods compatible with that combination;
- disables incompatible methods, with the reason shown on the entry — for example, a non-CSV staging format or a destination driver that does not match the provider;
- warns for database-executed methods that the resolved file path must be accessible to the database server — the key operational difference from client-side streaming.
Generate the SQL
- Select a method and adjust its options; each field has a default and an explanation.
- Review the Generated Bulk Load SQL preview.
- Click Use Generated SQL. If the field already contains a non-empty value, Etlworks asks for confirmation (Replace Bulk Load SQL) before replacing it.
The generated value lands in the Bulk Load SQL field and remains directly editable — the Builder is a starting point, not a lock-in.