In the given DataStage scenario choice should always be copy stage. Copy stage can be used to output data into multiple links however it would be best practice to use the same stage. When we use copy stage into job design DataStage does not take extra efforts to for it. Using copy stage will not degrade the performance as well.
Using transformer stage in a job would invoke the c++ compiler to compile the job as well as it will take time to compile (not to run). But if the requirement is just for renaming the columns them copy stage would be best suitable as it will only assign the copy operator in the back end score of the job.
In the given DataStage scenario choice should always be copy stage. Copy stage can be used to output data into multiple links however it would be best practice to use the same stage. When we use copy stage into job design DataStage does not take extra efforts to for it. Using copy stage will not degrade the performance as well.
ReplyDeleteUsing transformer stage in a job would invoke the c++ compiler to compile the job as well as it will take time to compile (not to run). But if the requirement is just for renaming the columns them copy stage would be best suitable as it will only assign the copy operator in the back end score of the job.
ReplyDelete