Property | Description |
|---|---|
Tracing Level | Determines the detail level of error and status messages written to the Activity Log. You can choose terse, normal, verbose initialization, or verbose data. Default is normal. |
Lookup SQL Override | Overrides the default SQL statement to query the lookup table. Specifies the SQL statement you want to use for querying lookup values. Use with Lookup Cache Enabled. |
Lookup Source Filter | Restricts the lookups based on the value of data in any field in the Lookup transformation. Use with Lookup Cache Enabled. |
Lookup Caching Enabled | Determines whether to cache lookup data during the runtime session. When you enable caching, the Data Integration Server queries the lookup source once and caches the values for use during the session. Caching the lookup values can improve session performance. When you disable caching, each time a row passes into the transformation, a SELECT statement gets the lookup values. Note: Flat file lookups and the pipeline lookups are always cached. Default is enabled. |
Lookup Cache Directory Name | Specifies the directory to store cached lookup data when you select Lookup Caching Enabled. The directory name can be an environment variable. |
Lookup Data Cache Size | Sets the maximum size the agent allocates to the data cache in memory. Select Auto to determine the cache size at runtime. Select Value to specify a maximum amount of memory to allocate to the cache. If the server cannot allocate the specified maximum amount when the session is initialized, the session fails. When the cached data is more than the available memory, it is paged to disk. Default is Auto. |
Lookup Index Cache Size | Sets the maximum size the agent allocates to the index cache in memory. Select Auto to determine the cache size at runtime. Select Value to specify a maximum amount of memory to allocate to the cache. If the server cannot allocate the specified maximum amount when the session is initialized, the session fails. When the cached data is more than the available memory, it is paged to disk. Default is Auto. Default is Auto. |
Datetime Format | Sets the datetime format and field width. Milliseconds, microseconds, or nanoseconds formats have a field width of 29. If you do not specify a datetime format here, you can enter any datetime format for fields. Default is YYYY-MM-DD HH24:MI:SS. The format does not change the size of the field. Default is YYYY-MM-DD HH24:MI:SS. The Datetime format does not change the size of the field. |
Thousand Separator | Specifies the thousand separator. Enter a comma (,) a period (.) or None. Default is None. |
Decimal Separator | Specifies the decimal separator. Enter a comma (,) or a period (.). Default is period. |
Case Sensitive String Comparison | Determines whether to enable case-sensitive string comparisons when you perform lookups on string columns in flat files. For relational lookups, the column types that support case-sensitive comparison depend on the database. |
Null Ordering | Determines how the null values are ordered. You can choose to sort null values high or low. By default, null values are sorted high. This overrides configuration to treat nulls in comparison operators as high, low, or null. For relational lookups, null ordering depends on the database default value. |
Sorted Input | Indicates whether or not the lookup file data is in sorted order. This increases lookup performance for file lookups. If you enable sorted input and the condition columns are not grouped, the session fails. If the condition columns are grouped but not sorted, the lookup is processed as if you did not configure sorted input. |
Pre-build Lookup Cache | Specifies to build the lookup cache before the Lookup transformation receives data. Multiple lookup cache files can be built at the same time to improve performance. |
Subsecond Precision | Sets the subsecond precision for datetime fields. For relational lookups, you can change the precision for databases that have an editable scale for datetime data. You can change the subsecond precision for Oracle Timestamp, Informix Datetime, and Teradata Timestamp data types. Enter a positive integer value from 0 to 9. Default is 6 microseconds. If you enable pushdown optimization in a task, the database returns the complete datetime value, regardless of the subsecond precision setting. |
Optional | Determines whether the transformation is optional. If a transformation is optional and there are no incoming fields, the task can run and the data can go through another branch in the data flow. If a transformation is required and there are no incoming fields, the task fails. For example, you might configure a parameter for the source connection. In one branch of the data flow, you add a Lookup transformation with a field rule so that only Date/Time data enters the transformation. You specify that the Lookup transformation is optional. When you configure the Mapping Configuration task, you select a source that does not have Date/Time data. The Mapping Configuration task ignores the branch with the Lookup transformation, and the data flow continues through another branch of the mapping. |