Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 26 Aug 2003 @ 11:11:49 GMT


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


Subj:   Re: Timeout using OLEDB and Microsoft Analysis Services
 
From:   Bob Doss

Hi Craig,

When are you getting the timeout messages? During builds or in Analysis Manager?

One tip, if you are attempting to migrate dimension keys to your fact table (a good practice BTW - avoids joining dimensions during builds) using Analysis Manager, AS will issue a 'select column from fact_table where 1=0' in order to get the datatype etc of the key in the fact table to make sure it is the same type as you defined in the dimension. Recent versions of Teradata are a bit smarter about recognizing that 1 != 0 - but if you are using a view for your fact table (say to create a virtual fact over an ER model or to outer join dimension tables) - chances increase that the Teradata optimizer will miss the 1=0 and do a table scan . Unfortunately, there is a hard coded timeout (about a minute) in Analysis Manager that is interpreted as an error. If you hit this you can dummy your view to select one PI value while you are working with Analysis Manager.

If you can give some more specifics about when you get the timeouts I may be able to help.


Hope this helps,

Bob



     
  <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: 15 Jun 2023