DSXchange

If the partitions are not balanced properly, then surrogate key stage will generate the values with holes in the range. If you want to generate the keys without any holes you should achieve perfect balance of records in the partitioning or you can use round robin partitioning while reading the data ...

I believe we can use it.

As others said you can only restrict the data going to the stages but cannot tell the job to discard the stages during the job run.

Peek stage is development/debug stage. It is mainly used for debugging and it can also be used for monitoring the progress of your application.
For more Information refer to Parallel Job Developer's Guide.

Peek stage is development/debug stage. It is mainly used for debugging and it can also be used for monitoring the progress of your application.
For more Information refer to Parallel Job Developer's Guide.

This design is working fine if the number of rows is less. For my case I will have maximum 20,000 rows and so I believe this implementation is ok.
For better performance (Improving the run time),I need inputs from experts here.

I believe the answer will be:
Yes, the records of previous partition will be there in the same partition after transformation stage.

Please put your code design in code tags.

Somebody might be monitoring the jobs you used in the sequence.

Continuous Funnel combines the records of the input data in no guaranteed order.In Sort funnel we can either sort in ascending or descending but not both ( Sort order accepts only one fixed value). And so I have used Sequence Funnel to collect the data. If you use parallel sort stages before sequenc...

We cannot use sequences in our implementation. We are running these jobs in grid environment (shared nothing environment in which nodes are allocated at run time) and so as per our development guidelines we cannot use sequences.

The design is as follows: ASC_IND_PARM specifies whether to sort in Ascending or Descending order. If ASC_IND_PARM =1 then the data will be sent to Ascending sort stage (Sort Order set to Ascending) and If ASC_IND_PARM <>1 the data will be sent to Descending sort stage (Sort Order set to Descending)...

I have to sort the data either in ascending order or descending order based on parameter value. I tried to implement it with the following approach: In the transformer create two output links. If sorting to be done in Ascending enable the first link and pass the data to a sort stage and set sorting ...

Sai, Can you please let us know the venue details. Did you had chance to speak with Ray??

We don't have DataStage Standared Edition but we do have Datastage Server edition.

Please do a search in the forum or refer the following the following link for information on datastage products.

viewtopic.php?t=88879