DSXchange

12K POST.
Iam not sure my points can reach his total post counts. Increasing drastically. Transition period between 11K and 12K is amazingly small.
Its again time for web master to edit the home page.
Needless to say the name. (Atleast for years)

Run time column propagation doest help you to read from repository but just help to you propagate the metadata used at the initial stage to the target or the end stage as the name suggest. Datastage is metadata driven, hence its not possible to change metadata during run time. If you need help on ch...

Was it an observation for just a single run?
Network congestion by the time will make a big difference in Sparse lookup. Find the network traffic by pinging to the DB server from DS server.
If the data volume is the only change made, try to revert back to original condition.

You can even refer your other post for more details.

Search for Normalization and find the purpose of normalization. So that you may find th purpose of using key in the table. If you refer the word Surrogate in the dictionary, you may find it as 'Artifical', 'Synthetic'.... Natural key is the original key avalable in the table as primary key (Or compo...

This is to set the environmetal variable at run time. If you need to use the existing variable, you may include $ENV or $PROJDEF in you Job property. $ENV will Instructs DataStage to use the current setting for the environment variable. $PROJDEF - Will reflect the change in the value even after comp...

Give permission 775 (or 777 for testing) to the object file created.

So again here comes Ray

Got your point Craig :D

And what about this....

I guess you have selected the Object type as Library. Since you have created a object file select the object as the option.

Others were more familiare with Kim's routines and scripts that Kim do

And by the way, creating index will eat up more table space.

Are you able to access and view the data from the View from command prompt.

Not only transformer, all active stages are merged to a single process during compilation. Passive stages frame the boundary. All the transformation logic will be built in to a single process. There wont be pipeline parallelism among the stages.

Perhaps you can try with the key @ID