regarding aggregator stage

[vijaykumar]

hi gurus,
my design is ODBC---->AGGREGATOR----->ODBC----->JOB1
i want to make use of aggregator o/p and give it as i/p to job2 .
using aggregator stage iam calculating sum(sal).
iam bulding up another job in which i want to add extra column called sum(sal) (ie) i want to make use of o/p from job1.
instead of continuing the same job, iam designing another job.
ODBC---->TRANSFORMER---->ODBC---->JOB2
can anyone help me in design.
cheers;
vijay

[narasimha]

Is there any reason why you want to break this up into two jobs?
You could do it in one job.

Bu if you have to, what is stopping you from doing it?

Job1

Code: Select all

ODBC---->AGGREGATOR----->ODBC

Job2

Code: Select all

ODBC---->TRANSFORMER---->ODBC

The Target of your first job will the Source for your second job.

[us1aslam1us]

I don't think you need to create two jos for this. Use the aggregator to perform sum function by adding a column there itself.

Sam

[I_Server_Whale]

Instead of this !!!

hi gurus,
my design is ODBC---->AGGREGATOR----->ODBC----->JOB1
i want to make use of aggregator o/p and give it as i/p to job2 .
using aggregator stage iam calculating sum(sal).
iam bulding up another job in which i want to add extra column called sum(sal) (ie) i want to make use of o/p from job1.
instead of continuing the same job, iam designing another job.
ODBC---->TRANSFORMER---->ODBC---->JOB2
can anyone help me in design.
cheers;
vijay

How about putting it this way?

Hi gurus,

My design is

Code: Select all

ODBC---->AGGREGATOR----->ODBC----->JOB1 

I want to make use of aggregator o/p and give it as i/p to job2 .
Using aggregator stage iam calculating sum(sal).
I am bulding up another job in which I want to add extra column called sum(sal) i.e., I want to make use of the o/p from job1.

Instead of continuing the same job, I am designing another job.

Code: Select all

ODBC---->TRANSFORMER---->ODBC---->JOB2 

Can anyone help me in design?

cheers;
Vijay.

[us1aslam1us]

Whale,

He seems to be in a hurry to solve this!! (Or might be trying not to consume much space on the dsxchange server )But definitely that will help the person reading that.

Sam

[narasimha]

Whale,

Nice that you handled the case too, I always wanted to mention it, but you did it

[I_Server_Whale]

Whale,

He seems to be in a hurry to solve this!! (Or might be trying not to consume much space on the dsxchange server )But definitely that will help the person reading that.

Sam

Well! In trying to conserve space, the result is that the OP's messages/statements are difficult to decipher. And in turn, we all will reply a ton of times in order to get the gist of the question, thereby losing much more space. So, if the question is well framed in the first place, then there will be the right amount of replies, thereby conserving much more space.

Whale.

[us1aslam1us]

Totally Agree with you dude!!

[kumar_s]

I still dont get the exact question. In job1 a Aggregator been used and Sum(Sal) is calculated. In next job (Job2) the output of Job1 is used. What is the need to add a new column. If the output is aggregated, the sum(sal) will be available as one of the field.
Or if you want to add sum(sal) for certain group, you desing is justified.
And btw, what is the clarification that you need in the job design?

[DSguru2B]

Yea, even i didnt quite get the question.

[I_Server_Whale]

Whale,

Nice that you handled the case too, I always wanted to mention it, but you did it

Thanks!

Right! and especially,

Code: Select all

'I' <> 'i'