0 - 7 of 7 tags for mlppi

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.

Hi All


If a table is defined as MLPPI the constraint can be checked either from DBC.PartitioningConstraintsV or from DBC.IndexConstraintsV. 

There the ConstraintText feild holds the explanation in a certain format such as


/* nn bb cc */ partition_expression_i /* i  d+a */



Hi All


May be I have posted this question before in this forum, but I am reposting it because that time I did not get any reply. Now I have been asked in a technical meeting to suggest a solution. But I am still not sure how to decide this, as my understanding is still in grey area.


Hello all,
we hav a large table (CDRs) with PPI defined on timestamp containing date & time when a record was loaded in DW.

Have you ever struggled over whether, or how, to use a new database feature?  In this presentation, we’ll demonstrate how database query log (DBQL) data can help when it comes to determining candidates for MLPPI (Multi-Level Partitioned Primary Index) as well as the new Columnar Partitioning feature of Teradata 14.

One of the more difficult challenges in database management and administration is determining where and how to implement a new RDBMS feature or function. In this presentation we’ll look at the DBQL data available for evaluation of tables and columns used within a workload and how this data can be leveraged for determining candidates for MLPPI (Multi-Level Partitioned Primary Index).

I still remember when PPI was first introduced in V2R5 and all the questions that came up in my mind in terms of utilization and performance impact. Long time has passed and most of the Teradata systems nowadays have at least one large PPI table defined.