Delete
The Delete step permanently removes a row from a database so you can cleanse your data. In the Delete step, choose a field to compare against the values of incoming fields from another step. When the comparison requirements are satisfied, the database row is deleted. If multiple rows match, all rows with that value are deleted from the database.
General
The following table describes the general options for the Delete step.
Step name
Specifies the unique name of the Delete step on the canvas. You can customize the name or leave it as the default.
Connection
Select the name of a connected database from the drop-down list. Alternatively, you can:
Select Edit to update an existing database connection.
Select New to create a database connection.
Select Wizard to create a database connection using the wizard.
Target schema
Specify the schema of the table in the database.
Target table
Specify the name of the table in your database where you want to delete the data.
Commit size
Specify the commit batch size. This is the number of DELETE statements to perform before sending a COMMIT command to the database.
If blank or set to 0, the database determines the commit size. The default is 100.
Keys
The columns in the following table define the key(s) used to map the row(s) to delete.
Table field
Specify the target table field you want to compare against. The list is populated from the Target table columns.
Comparator
Specify the comparator to use. Depending on your database and target table settings, comparisons might be case-sensitive.
Available comparators:
=<><<=>>=LIKEBETWEENIS NULLIS NOT NULL
Stream field 1
Specify the incoming stream field that contains the value to compare against the Table field.
Stream field 2
Specify the incoming stream field to use as the second value for the BETWEEN comparison.
Get fields
Select to populate Stream field 1 and Stream field 2 from previous steps in your transformation.
For example, if the lookup value of QUANTITYORDERED is less than or equal to min_quantityordered, and the PRODUCTLINE values match, that QUANTITYORDERED row is deleted from the STG_SALES_DATA table.
Metadata injection support
This step supports metadata injection. You can use it with ETL metadata injection to pass metadata to your transformation at runtime.
Last updated
Was this helpful?

