PK on a teradata table

Data Modeling

PK on a teradata table

I have serveral tables that have 2 different columns that must be uniques.  Each of the unique columns is 2 columns index.  I know that one of the indexes will be my primary index.  I was wondering and wantint to know if you create a constraint of a PK on the other 2 columns that must be unique will this create a sub table like a USI.  I was reading and understand that Teradata treats a PK constraint as an implicit USI, does not say if it creates a subtable.  I do not want to really use a USI because of the loads are not meeting their SLA, trying to find a way to elimenate the USI, but if the PK will have the exact same effect no sense in doing that.  So I guess my question is does a PK constraint create a subtable?

2 REPLIES
Highlighted
Teradata Employee

Re: PK on a teradata table

Yes, a PK / Unique constraint will create a USI subtable.

Teradata Employee

Re: PK on a teradata table

If the loads are large bulk processes, then an alternative is to enforce the uniqueness in ELT processes rather than in the physical design of the table.