|
Archives of the TeradataForumMessage Posted: Wed, 08 Aug 2007 @ 22:40:18 GMT
Hi Anomy, I try to use only Teradata Load tools for my ETL work for a number of reasons: - Fastest possible load times. - Log files are very important for determining the cause for an error. - I try to stay away from stored procedures (try to find out what went wrong with a 500 line stored procedure, got me?). - I think upsert is a must have. - I prefer dealing with error tables than rejecting a whole load because of two dodgy rows. - Don't want/like lengthy rollbacks or huge transient journals. So most of my ETL looks like: - FastLoad -> FastExport -> Named Pipe -> Multiload - MultiLoad -> FastExport -> Named Pipe ->MultiLoad - Combinations of BTEQ's and Tpumps I do this because there is software that takes care of: - Handling tool error recovery (it's not that hard one you get the hang of it). - Converting error tables into readable format. - All the tools use a NOTIFY routine. This allows making the whole process automated. If you are starting from scratch there is a lot of work ahead of you (either approach you choose). Cheers, Cesar Ureta
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||