DSXchange

Is there something in Datastage that can copy objects(Tables) from one database to another. If there is change in the table (example , addition of a column) in the source database , there should not be any change in the Datastage job as the whole table gets copied.

Not aware of any such things. May be you can use Database sync utilities to do such activities and not use a ETL tool to do such things.

I dont think there is a direct method of doing it in datastage
But if you really want to use datastage for it, there is a way

You can write a stored procedure to move tables from one database to another.
Call this SP from datastage!

It's called Runtime Column Propagation and you get it in parallel jobs only.

ray.wurlod wrote:It's called Runtime Column Propagation and you get it in parallel jobs. ...

Runtime Column Propagation, meaning it happens at the runtime only or there are methods of doing it with the job metadata also.

loveojha2 wrote:Runtime Column Propagation, meaning it happens at the runtime only or...

Hence the name.

Yes there are ways of doing it with job metadata which is called RCP (Runtime Column Propagation)

loveojha2 wrote:

ray.wurlod wrote:It's called Runtime Column Propagation and you get it in parallel jobs. ...

Runtime Column Propagation, meaning it happens at the runtime only or there are methods of doing it with the job metadata also.

Runtime Column Propagation is valid ONLY AFTER YOUR INITIAL TABLE STRUCTURE IS DEFINED. that means the table needs to exist on the target database and in case of any additional columns that need to be added can be done using RCP..same with server also you can use a RTI I map creation specifics to do the same functionality.

Not true. If you use direct Read and Write methods, RCP will cause entire rows (all columns) to be propagated even in the absence of a schema file. That's one of the reasons it can be so dangerous! What if the rows have 5000 columns?!!