Invoking an select script through ODI -Cons and error logging
404rajneesh4u
posted onEnjoy great content like this and a lot more !
Signup for a free account to write a post / comment / upvote posts. Its simple and takes less than 5 seconds
Is ODI - Oracle data integrator ? General good practice is to push down the load to the DB Server whenever possible. With that said, since all of your source data in a DB (homogeneous) and i assume your target is the same DB as well. For this instance, I would strongly advise option-1, SQL is easier to write, maintain and migrate than an ETL mapping. And its much easier to check for errors and then handle it in SQL itself (eg. check for ISNULL and replace with "NA") Use ETL mappings when your sources are Heterogeneous. (multiple discrete file sources) |
Thanks npack, Yes ODI is -Oracle Data Integrator. May I know about a bit more? What about data lineage offered by ETL tool like ODI, I guess that benefit will be compromised? Also I am wondering if I would be able to get same level of detail in ODI log files as with option 2, do you think that option 1 will display limited details of error as compare to those offered by an ETL tool like ODI. Also what is your opinion , if it is wisely option to use ETL tool just as script invoker? Is it still worth to spend money for ETL tool when most of logic is part of SQL script? Thanks, Rajneesh |
Its fastest when you do it in SQL. Period! |
Post Comment