-Unique Primary Index (Dmy_Prmy_Indx) - I'm populating this Primary Index value with '1' for every row in the table

When I joined Table A to Table B on (Day_Cd/Curr_Cd), the optimizer would duplicate Table B to all AMPs then perform a single partition
hash join based upon the join condition (great performance, but hokey)

When I joined Table A to Table B on (Day_Cd/Curr_Cd), the optimizer would duplicate Table B to all AMPs then perform a single partition
hash join based upon the join condition (great performance, not hokey)

In summary
When the optimizer had better statistics about Day_Cd/Curr_Cd (via the creation of a NUSI), it avoided making the poor decision of
redistributing the large table to all amps based upon the primary index (or join columns) of the smaller table.

However, I had to create a NUSI on these join columns so that the optimizer didn't make a bad decisions. As you know, secondary indexes
on large table take lots of diskpspace, slow inserts, updates, deletes, and can sometimes degredate run time performance. The better
solution would be to collect statistics on these join columns without a secondary index (currently not possible because the we can only
collect stats on a single field if we don't build a secondary index.)

Other than the 'fake primary index of value 1'- (example 2) or a single table primary index, can you think of another way to avoid
redistributing a large table when joining (on multiple columns) to a small table without adding a secondary index to the large table based
upon the join condition to the smaller table?