Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 21 Feb 2005 @ 22:40:14 GMT


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


Subj:   Default charset in volatile tables
 
From:   Anomy Anom

<-- Anonymously Posted: Monday, February 21, 2005 17:40 -->

Hi all

We have noticed that despite all the system defaults being Latin, when creating a volatile table in the following manner the column with the case statement gets created with Unicode character set which causes poor performance in subsequent joins.

     create volatile table test as
     (
      select
       proc_d
      ,case when proc_d is null then 'Y' else 'N' end as Null_D
      from run_d
     ) with no data
     on commit preserve rows ;

Any ideas on why this happens? If we create the table first like this it is created as latin charset:

     create volatile table test
     (
      proc_d date
     ,Null_D char(1)
     )
     on commit preserve rows ;

We're on V2R4.1.

Cheers



     
  <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: 27 Dec 2016