Home Page for the TeradataForum
 
https:

Archives of the TeradataForum

Message Posted: Fri, 19 Apr 2002 @ 16:17:38 GMT


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


Subj:   Re: Nulls in a composite Primary Key deployed as a Primary Index
 
From:   Claybourne L. Barrineau

Teradata encourages that physical data model design (including index selection) should be dictated by data demographics and usage. In this way, many of us have Primary Indexes which differ from primary keys (a notion which other database users cringe at.)

Weigh the pros and cons, if the pros overweigh the cons, go ahead and include a nullable field as part of your composite primary index. Teradata made it possible; therefore, one would assume they envisioned various legitimate reasons to do so.

We work with lots of data sources from thrid-parties, I feel your pain. Work-arounds such as default values and surrogate keys can often complicate matters. Nullable fields in your composite primary index will cause some performance degradation, but its probably beats than the alternate.

My 2 Cents,

Claybourne Barrineau



     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 28 Jun 2020