Hi Trafodioneers, In many cases, we find that "UPDATE" is not that efficient, so sometimes we rewrite the "UPDATE" as "UPSERT".
However, if we only write part of columns in upsert, the query plan will get "TRAF_MERGE", which is still not efficient. Only if we write all the columns in upsert, the query plan can get good query plan, such as VSBB_UPSERT. If table has hundrends of columns, this is very complex for users. It is possible that upsert choose "TRAF_REPLACE" by default, at the same time, we keep the values which are not in upsert? Best regards, Yuan
