Archives of the TeradataForum

Message Posted: Thu, 29 Jun 2006 @ 17:29:34 GMT

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

<-- Anonymously Posted: Thursday, June 29, 2006 11:32 -->

I came across this in a teradata user documentation.

When a table is created with an NPPI, its rows are hashed to the appropriate AMPs and stored there in row hash order.

When a table is created with a PPI, its rows are hashed to the appropriate AMPs and then assigned to an appropriate partition based on the value of a partitioning expression defined by the user when the table was created or altered. Once assigned to a partition, the rows are stored in row hash order. Rows are ordered first by their partition number, then by row hash value within each partition.

I think, sorting on rowid or rowhash should be the same, unless there are hash synonyms. Secondary index subtables can be sorted based on VALUE or HASH.

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