"Consistency" is in the eyes of the beholder. Depending on your purpose, Merge is very flexible to do what you want. In the case of many to many merge, you many want to consider Proc SQL or Hash table. In this case, it could be tricky to maintain your "consistency", say if non-override is an less ambiguous option, all-override could be disastrous, which row you want to choose to Override from in the second table? the first, the last, or somewhere in the middle? However, if just doing many to one, Merge is capable to provide both options: For non-override, reversing the merge order will do; for all-override, then you need rename the STATE in the second table, and add a simple assign statement: STATE=STATE_1; of course you can choose dropping STATE_1 in the end. Haikuo Update: if you only want to Override those missing values, check UPDATE statement.
... View more
