Archives of the TeradataForum

Message Posted: Fri, 19 Oct 2007 @ 21:46:49 GMT

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

From the path this thread has taken, it does not sound like the record is a duplicate, only PI is a dup - bad news for a UPI. He gave an example a few emails ago that showed two rows with three columns each. The value in the second column was the only difference between the rows. Therefore, a SET table does not help - not a duplicate row. Therefore, he will still receive the duplicate UPI error when attempting to insert the second row with the same value where as a duplicate row would be quietly thrown away.

Regards,

Michael Larkins
Certified Teradata Master
Certified Teradata SQL Instructor

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