Archives of the TeradataForum
Message Posted: Fri, 22 Dec 2006 @ 19:35:00 GMT
We have a number of MLoad's that we're using to load different sales tables. For performance reasons, we decided to partition the primary indexes by date and found that our MLoad's would fail unless we added the partitioning date column to the where clause of the update statement. The way the source system is implemented, the date that we chose for partitioning does change on occasion, and so the where clause doesn't always find the right row to update. This is causing duplicate sales to be added to the system.
Is there a way to MLoad a table with a PPI where the partitioning column changes? E.g. exclude it from the where clause? We're a fairly new Teradata shop so I apologize if this is an ignorant question.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|