Archives of the TeradataForum
Message Posted: Fri, 22 Jun 2001 @ 17:52:46 GMT
I have found that, in my environment, if a table has more than 1000 rows, the optimizer almost never duplicates the rows on all amps. It seems to be the same in your case. So, I agree with the suggestion below, that if you can
a) remove unnecessary history from the exch. rate table
b) create a separate processing table(derived maybe?) with only the 150 relevant rows and use that in your join, the optimizer will duplicate the small table on all amps, and that should perform quite well.
Rajiv Devulapalli GAP Inc.,
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|