Yellowbrick Data Warehouse Connector > Mappings and mapping tasks with Yellowbrick Data Warehouse > Yellowbrick Data Warehouse targets in mappings
  

Yellowbrick Data Warehouse targets in mappings

To write data to Yellowbrick Data Warehouse, configure a Yellowbrick Data Warehouse object as the target in a mapping.
Specify the name and description of the Yellowbrick Data Warehouse target. Configure the target and advanced properties for the target object.
The following table describes the target properties that you can configure in a Target transformation:
Property
Description
Connection
Name of the target connection or create a connection parameter.
Target Type
Type of the target object. Select Single Object or Parameter.
If you select Parameter, 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
Name of the target object. You can select an existing target object from the displayed list.
Create New at Runtime property is not applicable.
Parameter
Select or create a parameter for the target object. Appears only when the target type is Parameter.
The following table describes the advanced target properties:
Property
Description
Truncate Target Table
Truncates the database target table before inserting new rows.
Select one of the following options:
  • - True - Truncates the target table before inserting all rows.
  • - False - Inserts new rows without truncating the target table.
Bulk Insert
Bulk inserts all source rows into the target table.
This option can be used in place of the Write Operation property.
Bulk Commit Interval Rows
The number of rows at which the Secure Agent applies the commit to the target. The default value of 0 means to use a single transaction. When the Write Operation is set to one of the ‘Bulk’ options, this value is used instead of the session attribute Commit Interval. For more information, see the Yellowbrick Documentation Library.
SchemaPolicy
Policy for naming the schemas for tables. Select one of the following options:
  • - None
  • - Specified
  • - FromImport
  • - FromConnection
SchemaName
Name of the schema. Required if you select Specified for SchemaPolicy.
Pre-SQL
The SQL command that you want to run before the session starts.
Post-SQL
The SQL command that you want to run after the session ends.
Combine non-bulk inserts
Select this property to automatically combine multiple INSERTtableVALUES(a,b); statements into a single statement.
For example, to insert values to multiple tables, you must enter the values in the following format:
INSERT table VALUES (a1, b1), (a2, b2), (a3, b3), …
Non-bulk write flush interval
The number of records to be sent to the database at a time. 0 means the connector will select automatically.
Write Operation
Defines how the source records update the target table.
Select from one of the following options:
  • - Bulk INSERT
  • - Bulk UPDATE
  • - Bulk DELETE
  • - Bulk UPSERT
  • - JDBC Data Driven
  • - 1.1.20 compatibility mode
This option can be used in place of the Bulk Insert property.
Perform Bulk Truncate In Txn
Required if you selected the Truncate Table and if you chose one of the Bulk options for Write operation.
When checked, the truncate occurs in the same transaction as the Bulk operation and not in a separate transaction before the Bulk Operation.
Bulk Duplicate Handler
Specifies how to handle duplicate source records. by entering one of the following options:
You can choose form the following options:
  • - <empty> or NONE: Do not handle the duplicate source records.
  • - RANDOM: Pick one of the duplicates to apply.
  • - FIRST: Pick the first duplicate in the workflow order.
  • - LAST: Pick the last duplicate in the workflow order.
  • - ORDER BY {sql clause}: Apply the given order to the duplicates and select the first record. Use ASC/DESC to get different orders.
TableName
The table to write to. If not specified, use the table name in the target definition. You must add the table name without quotes.
Note: Do not use this value to modify user-specific SQL snippets from other attribute fields, such as pre-SQL and post-SQL. You must ensure that the table name specified in the SQL snippets matches the table name specified here.
AdvWriteProps
Yellowbrick Support may want you to add special options. In such instances, they will show you how to do so in AdvWriteProps.
Note: The Yellowbrick output component has all of the string parsing and data type conversion capabilities as the ybload command line tool. This flexibility is not necessary inside Informatica toolsas they have their own robust mechanisms for string parsing and data type conversion, but the options are still available.