INSERT INTO statement, optionally preceded by a DELETE FROM statement.
There are other components that can write data to a table and may better suit your use case:
- To output data to a new table, use Rewrite Table.
- To replace the values of existing rows in a table, use Table Update.
Use case
The Table Output component supports two ways of writing data out to a table:- Making incremental data loads to an existing table. For example, appending today’s transactions to a sales table.
- Overwriting existing data with fresh data. For example, replacing a staging table’s data with the latest extracted file.
Properties
- Snowflake
- Databricks
- Amazon Redshift
A human-readable name for the component.
The Snowflake warehouse used to run the queries. The special value
[Environment Default] uses the warehouse defined in the environment. Read Overview of Warehouses to learn more.The Snowflake database. The special value
[Environment Default] uses the database defined in the environment. Read Databases, Tables and Views - Overview to learn more.The Snowflake schema. The special value
[Environment Default] uses the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.Select the output table. The available tables depend on the selected environment.
Select whether to cast types in the event of data type mismatches.
- Yes: If the source column type does not match the target table type, attempt to CAST the value to the required target type.
- No: Do not cast types (do not fix data type mismatches).
- Input Column: The source field from the input flow.
- Output Column: The target table’s output column to insert data into.
- Column: Select the output column(s) to sort by.
- Sort Order: Set the corresponding column to be ordered ascending (default) or descending.
- Append: Adds the records to the end of the table.
- Truncate: Empty existing rows in the target table before loading the incoming input rows. This operation may use either a TRUNCATE or DELETE FROM query, depending on whether the current flow is in a transaction or not. TRUNCATE is faster, and therefore preferred, but is not transaction-safe and is not used if a transaction is in progress.

