Skip to main content
The Truncate Table orchestration component removes all rows from a table or partitions, while keeping the table intact. The table must not be a view or an external or temporary table. Truncate is implemented in two different ways, depending on whether the current flow is in the middle of a database transaction or not. The first is by using a TRUNCATE statement. For more information, read TRUNCATE TABLE for Snowflake, TRUNCATE TABLE for Databricks, and TRUNCATE for Redshift, respectively. The second is by using a DELETE FROM statement, which is preferable if the current pipeline is using a transaction. For more information, read DELETE FROM for Snowflake, DELETE FROM for Databricks, and DELETE for Redshift, respectively.
  • A truncate operation is faster than a delete operation.
  • A truncate operation is not transaction safe—it cannot be rolled back.

​
Properties

​
Name
string
required
A human-readable name for the component.
​
Warehouse
drop-down
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.
​
Database
drop-down
The Snowflake database. The special value [Environment Default] uses the database defined in the environment. Read Databases, Tables and Views - Overview to learn more.
​
Schema
drop-down
required
The Snowflake schema. The special value [Environment Default] uses the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.
​
Target Table
dual-listbox
required
The tables you want to truncate.To use grid variables, select the Use Grid Variable checkbox at the bottom of the Target Table dialog.