FerencMantfeld
19th November 2009, 10:09 AM
One of our customers has an ETL job that they tried to run to pick up records. This was duplicated in that there were 4 other similar ETL tasks that needed to run.
One way to schedule this was to schedule individual ETL tasks for each ETL task.
A far effective approach was to create a Link Report which then acts as a job control batch and then add a line to run each of the ETL tasks. This link report can then be scheduled just like one would schedule a JCL job in the mainframe world, where there are multiple sequenced steps.
http://www.seemoredata.com/foruminages/LinkETL1.pngWhat we now have is job stream that will run 2 ETL's, one after the other. This can be scheduled as a normal report by the Administrator or the developer.
One way to schedule this was to schedule individual ETL tasks for each ETL task.
A far effective approach was to create a Link Report which then acts as a job control batch and then add a line to run each of the ETL tasks. This link report can then be scheduled just like one would schedule a JCL job in the mainframe world, where there are multiple sequenced steps.
http://www.seemoredata.com/foruminages/LinkETL1.pngWhat we now have is job stream that will run 2 ETL's, one after the other. This can be scheduled as a normal report by the Administrator or the developer.