Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Sun, 30 May 2004 @ 14:01:21 GMT

  <Prev Next>   <<First <Prev

Subj:   Re: Access Lock with PI Selection
From:   Anomy Anom

<-- Anonymously Posted: Friday, May 28, 2004 10:26 -->

We are on V2R.

But we are going to V2R5 in 2 weeks, so it looks like that may fix the issue, based on your explain? If so, good enough.

Just to provide the full explain of the PI select (which references one view that joins 2 tables):

     sel * from prod_vmdb.summ_customer where store_cd = '12' and customer_cd = '34567';

  1)First, we do a single-AMP JOIN step from Prod_Tables.Summ_Customer by way of the unique primary index "Prod_Tables.Summ_Customer.Store_CD = '12', Prod_Tables.Summ_Customer.Customer_CD = '34567 '" with no residual conditions, which is joined to Prod_Tables.LU_User by way of the unique primary index "Prod_Tables.LU_User.UserName = TRANSLATE((USER )USING UNICODE_TO_LATIN), Prod_Tables.LU_User.Store_CD = Prod_Tables.Summ_Customer.Store_CD" with an additional condition of ("Prod_Tables.LU_User.Store_CD = '12'"). Prod_Tables.Summ_Customer and Prod_Tables.LU_User are joined using a nested join, with a join condition of ("(1=1)"). The input table Prod_Tables.Summ_Customer will not be cached in memory. The result goes into Spool 1, which is built locally on that AMP. The size of Spool 1 is estimated with high confidence to be 1 row. The estimated time for this step is 0.18 seconds.  
  ->The contents of Spool 1 are sent back to the user as the result of statement 1. The total estimated time is 0.18 seconds.  

Thanks Dieter, I appreciate the info.

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