Integration Service loads targets based on primary key-foreign key constraints where possible.

If selected, the Integration Service caches PowerMart 3.5 LOOKUP functions in the mapping, overriding mapping-level LOOKUP configurations.

If not selected, the Integration Service performs lookups on a row-by-row basis, unless otherwise specified in the mapping.

Size of buffer blocks used to move data from sources to targets. By default, this value is set to auto.

You can specify auto or a numeric value. The default unit is bytes. Append KB, MB, or GB to the value to specify other units. For example, 1048576 or 1024KB or 1MB.

Number of bytes that the PowerCenter Integration Service reads for each line. Increase this setting from the default of 1024 bytes if source flat file records are larger than 1024 bytes.

The maximum number of partial log files to save. Configure this option with Session Log File Max Size or Session Log File Max Time Period. Default is one.

Maximum memory allocated for automatic cache when you configure the Integration Service to determine session cache size at run time.

You enable automatic memory settings by configuring a value for this attribute. The default unit is bytes. Append KB, MB, or GB to the value to specify other units. For example, 1048576 or 1024KB or 1MB.

Maximum percentage of memory allocated for automatic cache when you configure the Integration Service to determine session cache size at run time.

Restricts the number of pipelines that the Integration Service can create concurrently to pre-build lookup caches. Configure this property when the Pre-build Lookup Cache property is enabled for a session or transformation.

When the Pre-build Lookup Cache property is enabled, the Integration Service creates a lookup cache before the Lookup transformation receives the data. If the session has multiple Lookup transformations, the Integration Service creates an additional pipeline for each lookup cache that it builds.

To configure the number of pipelines that the Integration Service can create concurrently, select Auto or enter a numeric value:

Configure custom properties of the Integration Service for the session. You can override custom properties that the Integration Service uses after the DTM process has started. The Integration Service also writes the override value of the property to the session log.

Allows the Integration Service to build the lookup cache before the Lookup transformation receives the data. The Integration Service can build multiple lookup cache files at the same time to improve performance.

You can configure this option in the mapping or the session. The Integration Service uses the session-level setting if you configure the Lookup transformation option as Auto.

Configure one of the following options:

You must configure the number of pipelines that the Integration Service can build concurrently. Configure the Additional Concurrent Pipelines for Lookup Cache Creation session property. The Integration Service can pre-build lookup cache if this property is greater than zero.

Date time format defined in the session configuration object. Default format specifies microseconds: MM/DD/YYYY HH24:MI:SS.US.

You can specify seconds, milliseconds, or nanoseconds.

MM/DD/YYYY HH24:MI:SS, specifies seconds.

MM/DD/YYYY HH24:MI:SS.MS, specifies milliseconds.

MM/DD/YYYY HH24:MI:SS.US, specifies microseconds.

MM/DD/YYYY HH24:MI:SS.NS, specifies nanoseconds.

Trims subseconds to maintain compatibility with versions prior to 8.5. The Integration Service converts the Oracle Timestamp datatype to the Oracle Date datatype. The Integration Service trims subsecond data for the following sources, targets, and transformations:

Default is disabled.