ETL Job v/s Stored Procedure
Posted: Tue Aug 16, 2011 5:40 pm
Hi All,
I have a query regarding the tuning a datastage job.
My requirement is to read 10 millions of data from a table and do a lookup (Left outer join) on some other table which is on same database, then insert the data into some other table.
My ETL job for above requirement is taking more than 10 mins time to process it.
My Query is
As all the tables (Source, Lookup and Target) are on same database, If I write a stored procedure for doing the same join in SQL query and insert into a table through stored procedure, is it increase the performance?
As we are using the Database concepts for loading and join, is it benefit anything in performance?
Can any one clarify?
I have a query regarding the tuning a datastage job.
My requirement is to read 10 millions of data from a table and do a lookup (Left outer join) on some other table which is on same database, then insert the data into some other table.
My ETL job for above requirement is taking more than 10 mins time to process it.
My Query is
As all the tables (Source, Lookup and Target) are on same database, If I write a stored procedure for doing the same join in SQL query and insert into a table through stored procedure, is it increase the performance?
As we are using the Database concepts for loading and join, is it benefit anything in performance?
Can any one clarify?