Doubt regarding PPI....
Teradata Teradata Discussion Forums Teradata.com Discussion Forum
Visit Teradata.com
Home       Guidelines    Member List
Welcome Guest ( Login | Register )
        


This online forum is for user-to-user discussions of Teradata products, and is not an official customer support channel for Teradata. If you require direct assistance, please contact Teradata support.


Doubt regarding PPI.... Expand / Collapse
Author
Message
Posted 2/24/2006 4:20:59 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 8/24/2006 2:07:00 AM
Posts: 4, Visits: 1
Hi,

I have some doubt in PPI....
If PPI is not a column of the PI, then the PI must be a Non-Unique Primary Index (NUPI).

Can some one explain the logic behind this concept in detail....


Post #3593
Posted 2/24/2006 5:16:12 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 1/23/2008 2:27:03 AM
Posts: 2, Visits: 3
If PPI is not a column of the PI, then the PI must be a Non-Unique Primary Index (NUPI).


So, what you want the statement above is right, do you want to change it from NUPI to other thing or you want the explaination saying that why the PPI is not a column of the PI.


Regards
Ramakrishna


Regards

RK

Post #3594
Posted 2/24/2006 5:28:32 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 8/24/2006 2:07:00 AM
Posts: 4, Visits: 1
Hi,

I just want to know why this is so...

Post #3595
Posted 2/24/2006 8:21:23 AM
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: 6/9/2008 2:55:55 PM
Posts: 185, Visits: 2
I believe that this was done to keep performance optimal on inserts/updates. If you could create a UPI that did not include the PPI column, then each insert (or update of the primary index columns) would have to go through each partition to make sure that the primary index values for the row were unique. This would be a lot of overhead for each insert and/or update of the PI columns.

You can create a USI on the unique columns if you want to enforce this. Since the USI subtable is arranged in hashing order on each AMP, a duplicate row would be detected most likley in the same data block.

That would be my guess.

Barry

Post #3601
« Prev Topic | Next Topic »


Reading This Topic Expand / Collapse
Active Users: 0 ( 0 guests, 0 members, 0 anonymous members )
No members currently viewing this topic.


All times are GMT -5:00, Time now is 10:11pm

Powered By InstantForum.NET v4.1.4 © 2008
Execution: 0.031. 7 queries. Compression Disabled.