Search found 9 matches

by juliank
Wed Apr 23, 2008 2:06 pm
Forum: General
Topic: Migration from OWB to DataStage
Replies: 14
Views: 10677

vmcburney wrote:Plus there will be a number of things DataStage can do that OWB cannot do.
Do you know of any comparisons that list these differences?
by juliank
Fri Apr 11, 2008 1:33 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Join - dealing with different input column names
Replies: 9
Views: 3016

Are you getting any error or warning? What is the stage prior to the Join stage? I don't get any error during the design stage. When I pull down the menu for keys to join, the list is blank even that I changed the input names to match where required. I don't know whether this a bug, or something th...
by juliank
Fri Apr 11, 2008 1:18 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Join - dealing with different input column names
Replies: 9
Views: 3016

... If you rename the column in Join input stage, output stage of the previous gets changed, and hence the actual rename is happening in the previous stage. Agree. So if a rename was made, and I see it, why wouldn't it be enough to accomplish now a join on columns that have identical names on the i...
by juliank
Fri Apr 11, 2008 9:34 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Join - dealing with different input column names
Replies: 9
Views: 3016

Thanks!

Do you maybe know what is the point of allowing to rename column names in a join (Input -> Columns), but not being able to take advantage of it? Maybe I am missing something.

Also, is there a performance penalty for using one or the other stage for something simple like renaming columns?
by juliank
Fri Apr 11, 2008 9:20 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Join - dealing with different input column names
Replies: 9
Views: 3016

Join - dealing with different input column names

What are the best practices for dealing with joins where the incoming column names don't match? Is there more than one approach? I thought that renaming column(s) under the input tab for a join will work, but it doesn't. If this is the case, which stage(s) are best suited to do this? Thanks for any ...
by juliank
Tue Apr 08, 2008 1:28 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Get Max Value using Transaformer stage.
Replies: 13
Views: 24206

:? Why not just select only the max record in Oracle? Great question - at least for me. I was looking for posts on 'max' and found this one. I am new to DataStage. One of the questions I am pondering over is where to have most of the logic? Keep most in Oracle or have most in one place for streamli...
by juliank
Thu Feb 28, 2008 7:43 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Case expression?
Replies: 4
Views: 1732

Thanks! And where do you actually place it, i.e. what stage or stages can one use?
by juliank
Wed Feb 27, 2008 3:25 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Case expression?
Replies: 4
Views: 1732

Case expression?

I am new to DataStage ... I am migrating an existing ETL to DataStage. Have a spot where there is a case expression between a source table and a target table. How do I implement a case expression in DataStage, e.g. something like this: CASE WHEN col1 IS NOT NULL AND col2 IS NOT NULL AND col3 IS NOT ...
by juliank
Wed Feb 27, 2008 3:07 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: [b]shall we use the peek stage as a target[/b]
Replies: 7
Views: 2976

Re: not getting exactly

not getting exactly. There isn't really antyhing that needs to be added to Ray's posts, but let me try from a newbie perspective... I just started using DataStage and finding the Peek stage very helpfull when developing jobs in steps. Say, if you start from left and don't know what will be exactly ...