Archives of the TeradataForum

Message Posted: Tue, 29 Nov 2005 @ 21:38:24 GMT

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

<-- Anonymously Posted: Tuesday, November 29, 2005 16:38 -->

145 bytes, no varchar, 20 columns with compression on zero values. The datablocksize is the default size (SHOW TABLE does not give a number).

The original table had a NUPI & USI but we all know by now that USI's are the kiss of death for bulk processing of 20M rows on a table with 3B rows and a USI defined.

After numerous complaints (as in will the INSERT of 20M rows finish before I retire), the table was then modified to MULTISET by the vendor while preserving the NUPI. That was done to get around the USI problem and maintain the data distribution for the ungodly aggregates performed on denormalized tables done by scanning 3B rows and joining with other tables.

PPIs anyone? May not be an option for them since they don't know what it will do to the application OTHER THAN HELP, perhaps!

Anyhow, I guess the main drawback of MULTISETs (besides violating relational set theory) and you confirmed that processing time must be spent checking for dups prior to the insert/update and in auditing the table regularly checking for dups (Argh!!!)

Thanks for the feedback.

Anonym

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