Archives of the TeradataForum

Message Posted: Tue, 02 Jun 2009 @ 12:16:33 GMT

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

Hi Craig,

Thanks for the response - I'm actually tending to the view that the bottleneck is the informatica mapping and not mload.

The table is a set table with UPI and the data is almost perfectly distributed across the amps.

I don't think we can do anything about the UPI/set since that's a business constraint.

The table is not empty in any of the loads.

BTW - does anyone know what sort of locks apply to the target table in an mload job? It appears to me that while MLOAD is running, we may have data being loaded into the Teradata table via an ODBC connection - is this possible and if so, how would impact on the performance of MLOAD?

Thanks again!

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