Sorter Transformation
You can sort
data with the Sorter transformation. You can sort data in ascending or
descending order according to a specified sort key. You can also configure the
Sorter transformation for case-sensitive sorting, and specify whether the output
rows should be distinct. The Sorter transformation is an active transformation.
It must be connected to the data flow.you can sort
data from relational or flat file sources.you can also use the Sorter transformation to sort data passing through an
Aggregator transformation configured to use sorted input.When you
create a Sorter transformation in a mapping, you specify one or more ports as a
sort key and configure each sort key port to sort in ascending or descending
order.
Transformation type:
Active
Connected
Port :
Input,output,key,direction(asc or desc)
Properties :
Active
Connected
Port :
Input,output,key,direction(asc or desc)
Properties :
Sorter Cache Size
The
Integration Service uses the Sorter Cache Size property to determine the maximum
amount of memory it can allocate to perform the sort operation. The Integration
Service passes all incoming data into the Sorter transformation before it
performs the sort operation.session cache size is 2 GB (2,147,483,648 bytes) or greater.allocate at least 16 MB (16,777,216 bytes) of physical memory to sort data using
the Sorter transformation.Sorter cache size is set to 16,777,216 bytes by default.
Use the
following formula to determine the size of incoming data:
number_of_input_rows [( S column_size) + 16]
Case Sensitive
The Case Sensitive property determines whether the Integration Service considers case when sorting data. When you enable the Case Sensitive property, the Integration Service sorts uppercase characters higher than lowercase characters.
Work Directory
You must specify a work directory the Integration Service uses to create temporary files while it sorts data. After the Integration Service sorts the data, it deletes the temporary files. You can specify any directory on the Integration Service machine to use as a work directory. By default, the Integration Service uses the value specified for the $PMTempDir process variable.
Distinct Output Rows
You can configure the Sorter transformation to treat output rows as distinct. If you configure the Sorter transformation for distinct output rows, the Mapping Designer configures all ports as part of the sort key. The Integration Service discards duplicate rows compared during the sort operation.
Tracing Level
Configure the Sorter transformation tracing level to control the number and type of Sorter error and status messages the Integration Service writes to the session log. At Normal tracing level, the Integration Service writes the size of the row passed to the Sorter transformation and the amount of memory the sorter transformation allocates for the sort operation. The Integration Service also writes the time and date when it passes the first and last input rows to the Sorter transformation.
Null Treated Low
You can configure the way the Sorter transformation treats null values. Enable this property if you want the Integration Service to treat null values as lower than any other value when it performs the sort operation. Disable this option if you want the Integration Service to treat null values as higher than anyother value.
Transformation Scope
The transformation scope specifies how the Integration Service applies the transformation logic to incoming data:
Transaction. Applies the transformation logic to all rows in a transaction. Choose Transaction when a row of data depends on all rows in the same transaction, but does not depend on rows in other transactions.
All Input. Applies the transformation logic on all incoming data. When you choose All Input, the PowerCenter drops incoming transaction boundaries. Choose All Input when a row of data depends on all rows in the source.
number_of_input_rows [( S column_size) + 16]
Case Sensitive
The Case Sensitive property determines whether the Integration Service considers case when sorting data. When you enable the Case Sensitive property, the Integration Service sorts uppercase characters higher than lowercase characters.
Work Directory
You must specify a work directory the Integration Service uses to create temporary files while it sorts data. After the Integration Service sorts the data, it deletes the temporary files. You can specify any directory on the Integration Service machine to use as a work directory. By default, the Integration Service uses the value specified for the $PMTempDir process variable.
Distinct Output Rows
You can configure the Sorter transformation to treat output rows as distinct. If you configure the Sorter transformation for distinct output rows, the Mapping Designer configures all ports as part of the sort key. The Integration Service discards duplicate rows compared during the sort operation.
Tracing Level
Configure the Sorter transformation tracing level to control the number and type of Sorter error and status messages the Integration Service writes to the session log. At Normal tracing level, the Integration Service writes the size of the row passed to the Sorter transformation and the amount of memory the sorter transformation allocates for the sort operation. The Integration Service also writes the time and date when it passes the first and last input rows to the Sorter transformation.
Null Treated Low
You can configure the way the Sorter transformation treats null values. Enable this property if you want the Integration Service to treat null values as lower than any other value when it performs the sort operation. Disable this option if you want the Integration Service to treat null values as higher than anyother value.
Transformation Scope
The transformation scope specifies how the Integration Service applies the transformation logic to incoming data:
Transaction. Applies the transformation logic to all rows in a transaction. Choose Transaction when a row of data depends on all rows in the same transaction, but does not depend on rows in other transactions.
All Input. Applies the transformation logic on all incoming data. When you choose All Input, the PowerCenter drops incoming transaction boundaries. Choose All Input when a row of data depends on all rows in the source.
Comments
Post a Comment