Data Integration-Free and PayGo
- Data Integration-Free and PayGo
- All Products
ASK INFAPreview
Please log in to access Ask INFA.
ASK INFAPreview
Property
| Description
|
|---|---|
Tracing Level
| Detail level of error and status messages that
Data Integration writes in the session log. You can choose terse, normal, verbose initialization, or verbose data. Default is normal.
|
Sorter Cache Size
| The maximum amount of memory required to perform the sort operation. The
mapping task passes all incoming data into the Sorter transformation before it performs the sort operation. If the
mapping task cannot allocate enough memory, the mapping fails.
You can configure a numeric value for the sorter cache. Allocate at least 16 MB of physical memory. Default is Auto.
|
Case Sensitive
| Determines whether the
mapping task considers case when sorting data. When you enable a case-sensitive sort, the
mapping task sorts uppercase characters higher than lowercase characters. Default is Case Sensitive.
|
Work Directory
| The
mapping task uses the work directory to create temporary files while it sorts data. After the
mapping task sorts data, it deletes the temporary files.
You can specify any directory on the Secure Agent machine to use as a work directory. Allocate at least 16 MB (16,777,216 bytes) of physical memory for the work directory. You can configure a system parameter or a user-defined parameter in this field. Default is the TempDir system parameter.
|
Distinct
| Treats output rows as distinct. If you configure the Sorter transformation for distinct output rows, the
mapping task configures all fields as part of the sort condition. The
mapping task discards duplicate rows compared during the sort operation.
|
Null Treated Low
| Treats a null value as lower than any other value. For example, if you configure a descending sort condition, rows with a null value in the sort field appear after all other rows.
|
Transformation Scope
| The transaction is determined by the commit or rollback point. The transformation scope specifies how the
mapping task applies the transformation logic to incoming data:
|
Optional
| Determines whether the transformation is optional. If a transformation is optional and there are no incoming fields, the
mapping 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 configure a parameter for the source connection. In one branch of the data flow, you add a transformation with a field rule so that only Date/Time data enters the transformation, and you specify that the transformation is optional. When you configure the
mapping task, you select a source that does not have Date/Time data. The
mapping task ignores the branch with the optional transformation, and the data flow continues through another branch of the mapping.
|
