Archives of the TeradataForum

Message Posted: Fri, 17 Mar 2006 @ 09:59:50 GMT

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

Ole, I think it might even be 10 for NPPI. Take, for example, the recent posting in the thread entitled "PPI and Master/Cylinder Index structures". I will quote one paragraph from it:

"At first sight secondary indexes structures would not need the Partition # for NPPI tables, but I guess that in order to have a standard row key layout (row key replaces the concept of row id, while formerly we had Row Hash + Uniqueness Value, we now have Partition #, + Row Hash + Uniqueness, the row key has 10 bytes as it has been explained earlier), probably when a new secondary index is built for NPPI it also includes the Partition # equal to zero, using the two additional bytes. I guess this dependes directly on the code."

OK, this is not a categoric statement yet but it does sound very plausible. For the sake of the uniform approach they might have added the 0- partition part even to NUSI on NPPI. It would be good to have this confirmed.

Anyway, it looks like the index size formulae in the "Database Design" manual need to be amended so that the changes made for partitioning are reflected there. The V2R6.0 version does not seem to be ? jour. I have not checked the V2R6.1.

Regards,

Victor

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