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, then all rows with that value are deleted from the database.
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.
Alternately, you can: |
|Target schema||Specify the schema of the table to load from your database.|
|Target table||Specify the name of the table in your database where you want to delete the data.|
|Commit size||Specify the size of the commit batch. The size is the number of
Depending on your connected
database, commit sizes can affect step performance. If blank or set to
The default is 100.
The key(s) to look up the value(s) table
The columns in the following table define the key(s) used to map the row(s) to delete.
|Table field||Specify the field name from the populated list of Target table columns for which you want to compare.|
|Comparator||Specify the comparator you want to use. Note that case-sensitive
comparisons are possible, depending on your connected database and Target
You can select one of the following comparators:
|Stream field 1||Specify the name of the field from the incoming stream that contains the row you want to use for comparison against the Table field value.|
|Stream field 2||Specify the name of the field from the incoming stream that
contains the row you want to use for the |
|Get fields||Select this button to populate Stream field 1 and Stream field 2 from previous steps in your transformation.|
For example, if the look up value of
QUANTITYORDERED is less than or equal
PRODUCTLINE values map
equally, then that
QUANTITYORDERED row is deleted from the
Metadata injection support
All fields of this step support metadata injection. You can use this step with ETL metadata injection to pass metadata to your transformation at runtime.