DSXchange

From the Parallel Framework Standard Practices Redbook: The Preserve Partitioning flag is an internal hint that Auto partitioning uses to attempt to preserve previously ordered data (for example, on the output of a parallel sort). This flag is set automatically by certain stages (sort, for example),...

We seem to be missing the 'below query'.

Then it wasn't added or set correctly, it would seem. Can you double-check that it was added to the job and the value you set it to? Also, one of the first log messages should show all of the environment variables in play when the job runs, is it listed there?

Shouldn't be the same... similar but not the same. Post the messages here.

Add $APT_DISABLE_COMBINATION to the job and set it to TRUE.

First you need to determine the bottleneck which may very well be in the job or the target rather than 'the extraction'. Use an @FALSE constraint so that nothing is done other than the reads, how long does it take then?

One example here.

Meaning an Execute Command stage in a Sequence job or a Before Job ExecSH in the job that will be loading them.

Unzip is unzip. Assuming you have to loop through multiple files you need a script and there's no reason to not let DataStage schedule/run/monitor that. If it's just one file, skip the script.

Write a script and let DataStage execute it.

If you have sorted the data but not made use of the KeyChange feature, then sure. But you don't really need the first stage variable: svRank--> if InputCode=svPrevious then svRank else svRank+1 svPrevious=InputCode Using all three won't hurt and may make it a teeny bit easier to read. With the KeyCh...

That's a standard group change detection task. Use stage variables in a transformer, one to track the previous group and one to increment your sequence when it changes. Use a Sort stage before it with a key change column in order to simplify the transformer work. In that case you would only need a s...

That's true... it doesn't always need to be enclosed as I noted and I forget where it doesn't want them. The expression editor always knows, however.

If myDateFormat is a job parameter, have you tried enclosing it in hash marks?
If it isn't then please explain how you are setting it up...

OK, sizes look 'fine'... time to check things out as Andy noted.