- Data Integration
- All Products
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.
|
Cache Directory
| Specifies the directory used to cache master or detail rows and the index to these rows.
By default,
Data Integration uses the directory entered in the Secure Agent $PMCacheDir property for the Data Integration Server. If you enter a new directory, make sure that the directory exists and contains enough disk space for the cache files. The directory can be on a mapped or mounted drive.
|
Null Ordering in Master
| Null ordering in the master pipeline. Select Null is Highest Value or Null is Lowest Value.
|
Null Ordering in Detail
| Null ordering in the detail pipeline. Select Null is Highest Value or Null is Lowest Value.
|
Data Cache Size
| Data cache size for the transformation. Select one of the following options:
Default is Auto.
|
Index Cache Size
| Index cache size for the transformation. Select one of the following options:
Default is Auto.
|
Sorted Input
| Specifies that data is sorted. Select this option to join sorted data, which can improve performance.
|
Master Sort Order
| Specifies the sort order of the master source data. Select Ascending if the master source data is in ascending order. If you select Ascending, enable sorted input. Default is Auto.
|
Transformation Scope
| Specifies how
Data Integration 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.
|
Why Sorted Input can improve performance?
Hi Koki Watanabe, Thanks so much for reaching out! This is explained in the following topic in the Data Integration Performance Tuning Guide: Optimizing joiner transformations
When you configure the Joiner transformation to use sorted data, Data Integration improves performance by minimizing disk input and output. You'll see the greatest performance improvement when you work with large data sets. For an unsorted Joiner transformation, designate the source with fewer rows as the master source.