Archives of the TeradataForum

Message Posted: Tue, 12 Aug 2003 @ 22:57:59 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

I've employed "Customize & Lock" approach in certain situations. Here are my observations:

1. The pipe goes away

2. Physical files become the Infa target

3. Capture the infa script from ./TgtFiles and customize it to read physical file (2).

4. Call locked code from Workflow as a command box

5. Could be a file management issue if files are large

6. Multiple mload .import files can merge many target files in 1 mload invocation

7. Restartability much improved from mload perpective

8. I've had the "buffer, wait" situation when many targets loading same table (solved with #6)

9. We redirect sysprint from locked script, so we can see mload output.

10. Analyze process - sometimes mega-benefits occur from staging the data on dbc and running transformations in SQL. Transformation script code can be called in your workflow and maybe deployed in parallel flows.

Improvements for Informatica

1. Show ldrlog output from mload in Workflow Monitor

2. Show sysprint from command boxes in Workflow Monitor

--
Dwight Etheridge
Teradata Certified Master

	<Prev	Next>		<<First	<Prev	Next>	Last>>