Archives of the TeradataForum

Message Posted: Thu, 17 Sep 2009 @ 14:06:07 GMT

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

Hi,

I have to agree with Victor on this point, my first reaction would be to use SQL. Keeps it nice and simple from a coding and operational perspective.

Some things to think about though:

1) You say 'millions' of rows, think more about the number of rows per AMP being updated. If you're doing 10 million rows on a 2000 amp system then it's only 5000 rows per amp - which is 'nothing' to Teradata. Conversely 10 million rows on a 10 amp system is a different proposition.

2) What proportion of the target table will be updated? 1%, 20% etc

3) Is this a one-off operation or a regular, batch process ?

Cheers,

Dave

Ward Analytics Ltd: Information in motion ( www.ward-analytics.com )

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