Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. Aggregator transformation
  7. Cleanse transformation
  8. Data Masking transformation
  9. Data Services transformation
  10. Deduplicate transformation
  11. Expression transformation
  12. Filter transformation
  13. Hierarchy Builder transformation
  14. Hierarchy Parser transformation
  15. Hierarchy Processor transformation
  16. Input transformation
  17. Java transformation
  18. Java transformation API reference
  19. Joiner transformation
  20. Labeler transformation
  21. Lookup transformation
  22. Machine Learning transformation
  23. Mapplet transformation
  24. Normalizer transformation
  25. Output transformation
  26. Parse transformation
  27. Python transformation
  28. Rank transformation
  29. Router transformation
  30. Rule Specification transformation
  31. Sequence Generator transformation
  32. Sorter transformation
  33. SQL transformation
  34. Structure Parser transformation
  35. Transaction Control transformation
  36. Union transformation
  37. Velocity transformation
  38. Verifier transformation
  39. Web Services transformation

Transformations

Transformations

Database target properties

Database target properties

You configure database target properties on the
Target
tab of the Properties panel.
The following table describes the database target properties:
Property
Description
Connection
Name of the target connection.
Alternatively, you can define a parameter, and then specify the connection in the mapping task.
Target Type
Target type, either single object or parameter.
Object
Name of the target object.
If you select a single object, you can also preview the data.
Operation
Target operation, either insert, update, upsert, delete, or data driven.
Truncate Target
Truncates the target object before inserting new rows.
Applies to insert and data driven operations.
Enable Target Bulk Load
Uses the database bulk API to perform an insert operation.
Use the bulk API to write large amounts of data to the database with a minimal number of API calls. Loading in bulk mode can improve performance, but it limits the ability to recover because no database logging occurs.
Applies to insert operations.
Update Columns
The fields to use as temporary primary key columns when you update, upsert, or delete target data. When you select more than one update column, the
mapping
task uses the AND operator with the update columns to identify matching rows.
Applies to update, upsert, delete and data driven operations.
Data Driven Condition
Enables you to define expressions that flag rows for an insert, update, delete, or reject operation.
For example, the following IIF statement flags a row for reject if the ID field is null. Otherwise, it flags the row for update:
IIF (ISNULL(ID), DD_REJECT, DD_UPDATE )
Applies to the data driven operation.
Forward Rejected Rows
Causes the
mapping
task to forward rejected rows to the reject file.
If you do not forward rejected rows, the
mapping
task drops rejected rows and writes them to the session log.
If you enable row error handling, the
mapping
task writes the rejected rows and the dropped rows to the row error logs. It does not generate a reject file. If you want to write the dropped rows to the session log in addition to the row error logs, you can enable verbose data tracing.
Pre SQL
SQL command to run against the target before reading data from the source.
You can enter a command of up to 5000 characters.
Post SQL
SQL command to run against the target after writing data to the target.
You can enter a command of up to 5000 characters.
Update Override
Overrides the default UPDATE statement for the target.
Enter the update statement. Alternatively, click
Configure
to generate the default UPDATE statement, and then modify the default statement.
The UPDATE statement that you enter overrides the default UPDATE statement that
Data Integration
uses to update targets based on key columns. You can define an override UPDATE statement to update target tables based on non-key columns.
Reject File Directory
Directory path to write the reject file. By default, the
mapping
task writes all reject files to the following service process variable directory:
$PMBadFileDir/<federated task ID>
If you specify both the directory and file name in the
Reject File Name
field, clear this field. The
mapping
task concatenates this field with the
Reject File Name
field when it runs the task.
Reject File Name
File name, or file name and path of the reject file. By default, the
mapping
task names the reject file after the target object name: <target name>.bad.
The
mapping
task concatenates this field with the
Reject File Directory
field when it runs the task. For example, if you have
C:\reject_file\
in the
Reject File Directory
field, and enter
filename.bad
in the
Reject File Name
field, the
mapping
task writes rejected rows to
C:\reject_file\filename.bad
.
For more information about database target properties, see the help for the appropriate connector.

0 COMMENTS

We’d like to hear from you!