Delete Table
This component allows you to delete a list of tables in a single operation.
This component may be used inside a transaction. Please note the following:
- On rollback, deleted tables will NOT be restored.
- On commit, the table is removed permanently. On rollback, it will be retained.
Snowflake: The Delete component has more in common with the Snowflake DROP TABLE statement than the DELETE statement.
Delta Lake on Databricks:
- Dropping tables from a data lake has the potential to destroy data.
- Dropping a managed table will remove the associated data that has been stored in the table.
- Dropping an unmanaged table simply removes the association between the table and the underlying data file—the file remains in place on the storage medium.
Amazon Redshift: The Delete component has more in common with the Amazon Redshift DROP TABLE statement than the DELETE statement. When deleting large amounts of table data, it is recommended you use a Vacuum component afterwards to save space on the cluster.
Google BigQuery: To learn about deleting tables in Google BigQuery, read Method: tables.delete.
Name = string
A human-readable name for the component.
Warehouse = drop-down
The Snowflake warehouse used to run the queries. The special value, [Environment Default], will use the warehouse defined in the environment. Read Overview of Warehouses to learn more.
Database = drop-down
The Snowflake database. The special value, [Environment Default], will use the database defined in the environment. Read Databases, Tables and Views - Overview to learn more.
Schema = drop-down
The Snowflake schema. The special value, [Environment Default], will use the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.
Tables to Delete = dual listbox
The tables to delete.
Ignore Missing = boolean
- Yes: If the table doesn't exist, ignore it.
- No: If a table doesn't exist, generate an error.
Name = string
A human-readable name for the component.
Catalog = drop-down
Select a Databricks Unity Catalog. The special value, [Environment Default], will use the catalog specified in the Matillion ETL environment setup. Selecting a catalog will determine which databases are available in the next parameter.
Database = drop-down
Select the Delta Lake database. The special value, [Environment Default], will use the database specified in the Matillion ETL environment setup.
Tables to Delete = dual listbox
The tables to delete.
Ignore Missing = boolean
- Yes: If the table doesn't exist, ignore it.
- No: If a table doesn't exist, generate an error.
Fail on Managed Delete = boolean
When Yes, the component will fail if the table being deleted is a managed table.
Name = string
A human-readable name for the component.
Schema = drop-down
Select the table schema. The special value, [Environment Default], will use the schema defined in the environment. For more information on using multiple schemas, read Schemas.
Tables to Delete = dual listbox
The tables to delete.
Cascade = boolean
Yes: Drop dependent objects such as any dependent views that have been manually created. No: Do not drop them. The component will fail at runtime if such objects exist and the table will not be removed.
Ignore Missing = boolean
- Yes: If the table doesn't exist, ignore it.
- No: If a table doesn't exist, generate an error.
Name = string
A human-readable name for the component.
Project = drop-down
Select the Google Cloud project. The special value, [Environment Default], will use the project defined in the environment. For more information, read Creating and managing projects.
Dataset = drop-down
Select the Google BigQuery dataset to load data into. The special value, [Environment Default], will use the dataset defined in the environment. For more information, read Introduction to datasets.
Tables to Delete = dual listbox
The tables to delete.
Ignore Missing = boolean
- Yes: If the table doesn't exist, ignore it.
- No: If a table doesn't exist, generate an error.
Name = string
A human-readable name for the component.
Schema = drop-down
Select the table schema. The special value, [Environment Default], will use the schema defined in the environment. For more information on schemas, read the Azure Synapse documentation.
Tables to Delete = dual listbox
The tables to delete.
Ignore Missing = boolean
- Yes: If the table doesn't exist, ignore it.
- No: If a table doesn't exist, generate an error.
| Snowflake | Delta Lake on Databricks | Amazon Redshift | Google BigQuery | Azure Synapse Analytics |
|---|---|---|---|---|
| ✅ | ✅ | ✅ | ✅ | ✅ |