× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2014

Re: SQL Merge vs. CPYF MBROPT(*UPDADD)

On 03-Feb-2014 13:14 -0800, Charles Wilt wrote:
I'm glad that DB2 for i finally got the SQL MERGE statement...

And I see that it offers lots of functionality...

However, for a basic merge i.e.
MERGE INTO archive ar
USING (SELECT activity, description FROM activities) ac
ON (ar.activity = ac.activity)
WHEN MATCHED THEN
UPDATE SET description = ac.description
WHEN NOT MATCHED THEN
INSERT (activity, description)
VALUES(ac.activity, ac.description)

I don't really see any benefits over CPYF MBROPT(*UPDADD)
FMT(*MAPDROP). Other than perhaps the ability to use commitment
control with merge.

Am I missing anything?

The Copy File (CPYF) utility has a requirement for a Unique key [constraint] on the target file. IIRC the MERGE does not have any key\index requirements. FWiW: The ability to participate under isolation is a common cause for needing to use SQL instead of the copy commands.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.