DSXchange

bcarlson wrote:That's not actually what I was thinking... You won't need to add a line terminator at all:

But the OP wants the data to be pivoted at every 5th position. How will that happen without concatenating the line terminators

shyamrai wrote:Yes sir, but I am not using the Job sequence. I am using the server job and ....

O yea, thats right.
Anywho, write a batch job to do your processing then. You will have greater control then.

Ok. Then it works like other enterprise stages. Great. But I dont see that in the OP's design. The main issue here is, that RohanSharma needs to explain how he designed the job to handle rejects.

You need to design your sequence that way then. Stick in an exception handler connected to a terminator activity. Do not handle the scenario in which the job finishes with warnings, in the conditional trigger. This way if a job finishes with warnings, the control will go to the execption handler whi...

The last zero in your parameters is the warning limit. Set that to 1.

Also try to make your job name small. Dont forget smaller link names. Try to split the job into two jobs. Try to play around with these.

You can set the warnining limit in the UtilityRunJob() to 1. So that your sequence job inherits this property and passes it down to the children jobs. This way, even if there is a single warning, your jobs will abort. But I am not sure about the entire design, but then again, thats not the topic of ...

It will be executed once per job. Before it actually starts executing the main sql thats in the sql tab. This is for the Before sql. The after sql will be executed once the stage has finished processing all the rows.

It will be once, before executing the main sql body.

urma wrote:
do you have another suggestion?

Yes, revert back, with full force, on such restrictions. You are sitting on a unix box and cannot utilize the power of unix utilities. I would feel crippled.

Sachin: Your method is valid in a server job and not in a parallel job.
RohanSharma: I do not see a reject link coming out of an ODBC stage? How exactly are you rejecting records? Does ODBC stage even support reject links ?

chulett wrote:Huh... I guess our definitions of the phrase 'most recent' differ.

Make the name of your stages shorter.

Do a group by on Id and Salary and get the MIN() of date.

Thats good thinking guys. Split it at the source and then add a line terminator after every record to pivot it.