Table Maintenance

[BillDHS]

I have a couple questions concerning table maintenance. I am ultimately trying to provide the fastest inserts while preventing dups.

Fastload into a SET table. Fastlaod by design drops duplicate rows. Does using a SET table also involve dup checks during the distribution step?

Can I use a MULTISET table and a UPI to prevent dups? Will the UPI cause only the UPI column checked instead of a bit by bit check? What if I use a MULTISET and a NUPI and a PK constraint on the same column (TD may not allow me to do this)?

 

[dnoeth]

If you Fastload a table there's no difference if it's SET or MULTISET, it's always removing dups. If there's a UPI it's only checking the UPI-columns else it's doing a duplicate row check. But this is only checking rows with the same RowHash, so the fastest way is having a UPI or a NUPI with just a few rows per value ;-)

Multiset/NUPI and PK:
You mean a PK over all columns in your table? This is similar to a SET table and you'd need more disk space for the USI than for the base table. And you can't have a USI during a Fastload...

Dieter