0 - 15 of 15 tags for partitioning

Hi All, 
I'm trying to come up with an OLAP function solution to a units deduction problem for various groups. 

Which of the following partitioning expression has a better performance while SELECT, INSERT operations ? Consider the table has data around couple of Terabytes.
PARTITION BY RANGE_N(LOAD_TIMESTAMP  BETWEEN TIMESTAMP '2015-01-01 00:00:00.000000' AND TIMESTAMP '3499-12-31 23:23:59.999999' EACH INTERVAL '1' DAY );

Teradata partitioning was originally released in V2R5.0. This presentation reviews partitioning and the changes to this feature (from DPE to columnar) that have occurred over the last twelve years.

Hi all,
I was extending the partition of some tables to host the 2015 and I have notice this strange behavior.
I have this table called Table1

I understand the PARTITION#Ln is used to denote a level in MLPPI.
What is the combined partitioning Expression ? Is this all the ranges specified in a MLPPI table. ?
How does the RowKey differ to the combined partition number. 
Teradata's documentation states the following.

I was suggested by DBA to change in one of tables , the partitioning column from timestamp to date.
In explain plan I can see that in both cases partition prunning takes place.
Is there anybody that is master in partitioning in teradata and can help if there is some logical reasoning for such change ?

In my blog entries "Teradata Columnar" and "9.2 Quintillion? What's that all about?", I discussed column partitioning and the increased partition limit that are introduced in TD 14.0.  But there are other TD 14.0 partitioning enhancements that you may find useful.  The following provides a brief introduction to these enhancements; for more detailed information, see the Orange Book: Increased Partition Limit and other Partitioning Enhancements, the Orange Book: Teradata Columnar, and the TD 14.0 manuals.

A quintillion is 10 raised to the power of 18 (that is, 1 followed by 18 zeros).  9.2 quintillion (or more precisely, 9,223,372,036,854,775,807) is the new limit in Teradata Database 14.0 for the number of combined partitions.  Note that this is the same as the maximum BIGINT value (which is a signed 8-byte integer).  While tables that are defined with 65

With row partitioning (for a PPI or column-partitioned table), the Teradata Database makes sure rows are placed in their appropriate partitions.  When the row partitioning for the table is altered, rows may need to move from one partition to another so they are in their appropriate partitions according to the altered partitioning.  The partitioning expression must be deterministic (always computes the same value for the same value of the partitioning column) to properly place and retrieve the row.

For instance if the table has RANGE_N partitioning, ALTER TABLE will move rows automatically from NO RANGE to newly-added ranges as needed.  Also, if a range is dropped, rows from that partition are moved to the NO RANGE, NO RANGE OR UNKNOWN partition or a newly-added range that covers the dropped range.

Teradata Database 14.0's new partition limit of 9223372036854775807 (over 9 quintillion) is coming!


Is there any way to partition directly on a small (ie. CHAR(3)) character column, without defining a CASE_N or RANGE_N for the column (ie. partition on all unique values of the column)?

I was recently asked about NO RANGE, UNKNOWN, and NO RANGE OR UNKNOWN partitions for the RANGE_N function.  While these have been available since TD V2R5.0, there is sometimes confusion about what they mean and when to use or not use them.

Why cannot a table's primary index be partitioned, if a hash index is defined
on the table?

I have been looking for answers to a basic question on table partitioning in Teradata. Can someone please shed more light. Here it is -