Regarding optimization, I have observed that on the Snowflake side, with Merge being used on a table that has micro partitions and has been well maintained, the statement execution will be very fast. This helps in both cost savings and performance-wise optimization. It would be beneficial if there is a common public community so that people who may not be aware of this will become more aware. Additionally, when we do joins within the Merge statement, there is always a chance of getting duplicates. Snowflake added a feature called QUALIFY that allows us to filter based on ranking and eliminate duplicate records. If such a feature were available in regular Merge statements within any database, that would be helpful. This would eliminate the need to rebuild another subquery inside the Merge statement.
