Data Integration Connectors
- Data Integration Connectors
- All Products
Property
| Description
|
---|---|
Connection
| Select an existing target connection, or create a target connection.
Alternatively, you can use a connection parameter in the mapping and then enter a specific connection in each mapping task that is associated with the mapping.
If you want to use a connection parameter with a specific target object, you must first select a specific connection so that you can access the target to select the target object in the
Object field. After you select the target object, define the connection parameter.
If you want to use parameters for both the connection and target object, you do not need to first select a specific connection. You can just define the parameters in either order.
To define a connection parameter, click
New Parameter and enter the following information:
|
Target Type
| Select
Single Object if you want to specify a target table.
Alternatively, select
Parameter and then specify an input parameter for the target object in the
Parameter property. When you use a parameter, you specify the target table for the parameterized object on the
Targets page of each mapping task associated with the mapping.
|
Object
| Click
Select . In the
Target Object dialog box, select
Existing and then select an existing target table.
Alternatively, select
Create New at Runtime and enter the name of a target table to generate at runtime. However, Informatica recommends that you do not use this option. The generated table might not be completely materialized with data the first time the mapping task runs. Also, with this setting, you cannot set the
Operation property to
Data Driven , which is required to properly handle subsequent insert, update, and delete records. After the table is generated, you must return to the
Object field, select
Existing and the generated target table, and then set the
Operation property to
Data Driven .
A generated target table contains the PowerExchange-generated DTL__ metadata fields from the source. If you do not want these columns on the target, you can configure a field rule that excludes the columns that have the "DTL__" prefix.
|
Parameter
| Select or create a parameter for the target object. Appears only when the target type is
Parameter .
|
Operation
| Select
Data Driven to properly handle insert, update, and delete records from the source.
By default, inserts, updates, and deletes are applied as inserts, updates, and deletes, respectively.
|
Data Driven Condition
| Enables you to define expressions that flag rows for an insert, update, delete, or reject operation. Appears only when the operation type is
Data Driven but is not required for this operation type.
|
Update Columns
| Click
Add to select the columns that you want to use as a logical primary key for performing update, upsert, and delete operations on the target. Appears only when the operation type is
Data Driven . This field is not required if the target table already has a primary key.
|
Truncate target
| Select this option if you want to clear the target table each time the mapping task runs. However, if you select this option and set the
Operation property to
Data Driven , update operations on the target will fail.
|
Advanced Property
| Description
|
---|---|
Forward Rejected Rows
| Select this option to have the Target transformation pass rejected records to a reject file that is generated in the following directory:
Clear this option to ignore the rejected records.
This field is not displayed if a parameter is specified for the target connection.
|
Pre SQL
| SQL statements that run on the target before the extracted data is written to a target.
Maximum length is 5000 characters.
|
Post SQL
| SQL statements that run on the target after the extracted data is written to a target.
Maximum length is 5000 characters.
|
Update Override
| An override SQL update statement to update the data in a target table. The override SQL update statement you specify overrides the default update statements that the Secure Agent uses to update targets based on key columns. You define an override update statement to update target tables based on non-key columns. In the override statement, you must enclose all reserved words in quotation marks.
|