Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 28 Jul 2006 @ 12:21:19 GMT


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


Subj:   Re: Oracle to Teradata Migration and Max Row Size
 
From:   Dieter Noeth

Praveen Chakrapani wrote:

  I think if we have row size more than 64KB then teradata splits and stores the row internally. There is no need to split up the table. I just created a table with rowsize more than 64kb and inserted few rows it worked fine.  


The maximum rowsize in Teradata is 64256 bytes (in V2R6.1 65536). It can't be exceeded because there are no row splits.


          > BTEQ -- Enter your DBC/SQL request or BTEQ command:
          > create table t4(a int, b int, c char(32000), d char(32000));
          >
          > create table t4(a int, b int, c char(32000), d char(32000));
          >
          >  *** Table has been created.
          >  *** Total elapsed time was 2 seconds.

Just a bit below the limit...

     create table t4(a int, b int, c char(32000), d char(32236));
      *** Failure 3933 The Maximum Possible Row Length in the Table is too Large.
  If row size is more than you have to increase the data block size according to that while creating the table. We can increase datablocksize to max of 127.5KB. This way you can store atleast one row in one datablock. But having many datablocks for a table may affect query performance also.  


Even if the datablocksize is 127.5 KB, the rowsize is still limited to 64256, because a part of the record is a word indicatinig the rowlength.


Dieter



     
  <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