Archives of the TeradataForum

Message Posted: Mon, 11 Feb 2002 @ 22:22:17 GMT

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

Actually you can get a significant performance gain at load time by making your table MULTISET because you're eliminating the cost of duplicate row checking. Even if your table is a SET TABLE, you might consider defining it as MULTISET if your upstream processes already assure that you won't have duplicate rows in your table.

I certainly feel that the performance gain offsets any manual auditing that has to be done to insure that a duplicate row hasn't been loaded. So if you can trust the upstream processes and your table is non-unique, then I would define the table as a MULTISET. If you can't be sure or want to be very safe, then define it as a SET TABLE.

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