datastage database usage
Posted: Fri Jan 21, 2005 3:54 am
My company are in the process of developing a d/w.
The sources for the data are a series of Sybase database, two sql servers and one access database.
Datastage will be used to transform the data and MS SQL 2K will host the d/w. These things are set in stone.
The question I have is regarding the transform database. I am aware that the Datastage jobs/transofrms will go to the source databases for their information but where should I store the data that comes back from these jobs ? Not all data will be available at the same time so some transforms will have to wait until all data has been collected.
Do I create a database schema within datastage and should I bring the data back to a separate sql server before transforming it ?
If both methods are possible then what are the pros/cons.
This is the one grey area that we have and as we are going through a process of "on the job training" any help would be appreciated here.
The sources for the data are a series of Sybase database, two sql servers and one access database.
Datastage will be used to transform the data and MS SQL 2K will host the d/w. These things are set in stone.
The question I have is regarding the transform database. I am aware that the Datastage jobs/transofrms will go to the source databases for their information but where should I store the data that comes back from these jobs ? Not all data will be available at the same time so some transforms will have to wait until all data has been collected.
Do I create a database schema within datastage and should I bring the data back to a separate sql server before transforming it ?
If both methods are possible then what are the pros/cons.
This is the one grey area that we have and as we are going through a process of "on the job training" any help would be appreciated here.