|
Archives of the TeradataForumMessage Posted: Tue, 19 Sep 2006 @ 09:25:20 GMT
Partitioning table does not guarantee that the optimizer has selected the partitioning strategy. The SQL that are written should reference them in where clause as a range constrains. More ever what I have seen is that if data requested is smaller, the partition elimination strategy works at its best. I also believe that if you typecast the partitioning column, optimizer no longer will reap the benefits of partition elimination. Last example will never select partitioning strategy as you have typecasted the partitioning column. The range constrain may not have worked because the date includes a timestamp format which is not specified in the partition expression. Thanks, Vinay Bagare
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||