|
Archives of the TeradataForumMessage Posted: Thu, 01 Nov 2007 @ 13:39:46 GMT
Hi Michael, Thanks for the reply. If I understand correctly, you are saying that by trying to force a null partition value to be not null (via coalesce) during a comparison, we would have been eliminating all records contained in the null partition in any case (even if it was technically possible to use coalesce on a partition column), due to partition elimination. In other words, we would be defeating the end objective in any case. Therefore we will have to ask the developers to a) choose a different partitioning column, or b) ensure we do not get null values (i.e. make the column not null). Care would also need to be taken to ensure that most of the records do not end up in the default partition (whether it's null or something else). Thanks once again for the valuable input. Regards Etienne Stieger
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||