08
Tue, Oct
2 New Articles

SQL MERGE Statement Tricks

Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Learn how to use MERGE to synchronize data between tables with just one SQL statement

by Rafael Victória-Pereira

Editor’s note: This article is excerpted from chapter 12 of SQL for IBM i: A Database Modernization Guide, by Rafael Victória-Pereira.

Often, we’re faced with the need to synchronize two tables, in such a way that the target table gets all the relevant information from the other one. For instance, imagine that you have an inventory table that receives daily updates from several stock movement tables. There are new entries to register (INSERT statements), but also item quantity fluctuations (UPDATE statements), which require separate processing. Naturally, you can also have some items disappearing from stock, and depending on how those situations are handled, these can be updates or actual deletes in the inventory table. With the MERGE statement, you can mash up those statements into a single one.

Anatomy of the MERGE Statement

Seems a bit farfetched, right? Well, once you get the hang of it, you’ll see that this two-for-the-price-of-one statement is very useful. But before you’re able to use it, you need to understand it, so let’s take look at the anatomy of the MERGE statement:

MERGE INTO <Target table name>

      USING <origin table or SELECT statement>

ON <matching columns>

      WHEN MATCHED <(optional) AND <comparisons>> THEN

            <Modified UPDATE or DELETE statement>

      WHEN NOT MATCHED <(optional) AND <comparisons>> THEN

            <Modified INSERT statement>

      ELSE IGNORE

This seems like a lot, so let’s go over it line by line, top to bottom:

  • MERGE INTO <target table name>—indicates the name of the table or updatable view over which the I/O actions will take place.
  • USING <origin table or SELECT statement>—indicates the exact opposite: instead of specifying where the data goes to, this line indicates where the data comes from. It can be a table name or a SELECT statement.
  • ON <matching columns>—This line is extremely important! It explains how the records in the origin and target tables will be matched, just like you’d do in an INNER JOIN instruction.
  • WHEN MATCHED <(optional) AND <comparisons>> THEN—This is where the fun begins. This and the next WHEN ... line are optional, but at least one of the two has to be specified. In its simplest form (WHEN MATCHED THEN), it indicates that the actions below it will be executed if the conditions stated in the ON <matching columns> line evaluate to true. Note that you can specify additional conditions to be evaluated in conjunction with the ones from the ON ... line. That’s where the <(optional) AND <comparisons>> bit comes into play. This may sound a bit confusing, but I’ll present an example that will help you understand what I mean.
  • <Modified UPDATE or DELETE statement>—If a match was found, then you can perform an UPDATE or DELETE. However, note that this won’t be a regular statement. It can only affect the table/view mentioned in the first line of the MERGE statement, so it doesn’t make sense to include the FROM clause here. It’s another of those peculiarities of the MERGE you’ll have to get used to.
  • WHEN NOT MATCHED <(optional) AND <comparisons>> THEN—the story for this one is similar to the WHEN MATCHED THEN, but in reverse: this specifies what should happen when the line from the origin table doesn’t match the requirements—that is, when the conditions in the “ON ...” line and (if you also specify them) the ones in the <(optional) AND <comparisons>> part of this line both evaluate to false.
  • <Modified INSERT statement>—If and only if a match was not found, then you can issue an INSERT statement. Keep in mind that this is also not a regular statement, because the FROM clause will be absent, as explained earlier.
  • ELSE IGNORE—This is the catch-all clause, which is used as an escape when the record doesn’t match any of the previous conditions. Note that you can have multiple WHEN MATCHED and/or WHEN NOT MATCHED conditions, as long as the <(optional) AND <comparisons>> part is different.

You’re probably scratching your head, thinking this is confusing. It’s a bit weird, I know. Let’s go over an example and try to clear things up.

The scenario I described earlier involves two tables: the temporary TEMP_TBL_PERSONS and the “real” TBL_PERSONS. What we want to do is update the second table with the data from the first one. With this, I’ve identified the origin and target tables, and I can start writing the MERGE statement:

MERGE INTO UMADB_CHP5.TBL_PERSONS PERSON

   USING UMADB_CHP5.TEMP_TBL_PERSONS T

The TBL_PERSONS table is the target table; I gave it the alias PERSON, while the TEMP_TBL_PERSONS, our origin table, has the alias T. I gave this table a short alias because we’re going to use it a whole lot, and a longer alias would get in the way.

Now let’s see how to match the records in both tables. I said earlier that the person ID, when the record is from an existing person in the database, is supplied in the Excel file. This is particularly handy because the Persons table primary key is the Person_Id column. With this piece of information, I can write the “ON ...” line:

       ON PERSON.PERSON_ID = T.PERSON_ID

Now let’s go over the rules again: if the person IDs between the temp table and the real one match, we can update the existing information with the one coming from the temp table. Let’s translate that into code:

   WHEN MATCHED THEN

       UPDATE SET PERSON.NAME = T.NAME,

                   PERSON.DATE_OF_BIRTH = T.DATE_OF_BIRTH,

                   PERSON.HOME_ADDRESS = T.HOME_ADDRESS,

                   PERSON.HOME_PHONE_NBR = T.HOME_PHONE_NBR,

                   PERSON.MOBILE_NBR = T.MOBILE_NBR,

                   PERSON.EMAIL_ADDRESS = T.EMAIL_ADDRESS,

                   PERSON.DRIVERS_LICENSE = T.DRIVERS_LICENSE,

                   PERSON.SOCIAL_SEC_NBR = T.SOCIAL_SEC_NBR

Because I don’t have additional conditions, I went for the simplest possible form of the MATCHED line: WHEN MATCHED THEN. The next few (OK, not so few) lines specify what happens when a match is found: I’ll update all the Persons table columns with their namesakes from the temporary table. Note that this is not a regular UPDATE statement—it’s missing the table name and WHERE clause.

The rules of the scenario described earlier also state that when a matching ID is not found, I should insert the new record in the target table. Coding this is also simple enough, but it has a catch:

   WHEN NOT MATCHED THEN

       INSERT (NAME,

               DATE_OF_BIRTH,

               HOME_ADDRESS,

              HOME_PHONE_NBR,

               MOBILE_NBR,

               EMAIL_ADDRESS,

               DRIVERS_LICENSE,

               SOCIAL_SEC_NBR)

       VALUES (T.NAME,

               T.DATE_OF_BIRTH,

               T.HOME_ADDRESS,

              T.HOME_PHONE_NBR,

               T.MOBILE_NBR,

               T.EMAIL_ADDRESS,

               T.DRIVERS_LICENSE,

               T.SOCIAL_SEC_NBR);

It’s not immediately obvious, so I’ll remind you of the rules: if a matching ID is not found, then I should insert the record. This means that the ID from the temporary table is useless. In other words, I don’t need to (and actually can’t) use it in the INSERT statement. This is not a problem, because the PERSON_ID column value is automatically generated by the database engine. Again, what you see here is a modified INSERT statement—it also lacks the FROM and WHERE clauses.

That’s it! I hope this example made clear how useful and easy (after some practice) the MERGE statement can be. Here’s the complete statement explained above:

MERGE INTO UMADB_CHP5.TBL_PERSONS PERSON

   USING UMADB_CHP5.TEMP_TBL_PERSONS T

       ON PERSON.PERSON_ID = T.PERSON_ID

   WHEN MATCHED THEN

       UPDATE SET PERSON.NAME = T.NAME,

                   PERSON.DATE_OF_BIRTH = T.DATE_OF_BIRTH,

                   PERSON.HOME_ADDRESS = T.HOME_ADDRESS,

                   PERSON.HOME_PHONE_NBR = T.HOME_PHONE_NBR,

                   PERSON.MOBILE_NBR = T.MOBILE_NBR,

                   PERSON.EMAIL_ADDRESS = T.EMAIL_ADDRESS,

                   PERSON.DRIVERS_LICENSE = T.DRIVERS_LICENSE,

                   PERSON.SOCIAL_SEC_NBR = T.SOCIAL_SEC_NBR

   WHEN NOT MATCHED THEN

       INSERT (NAME,

               DATE_OF_BIRTH,

               HOME_ADDRESS,

              HOME_PHONE_NBR,

               MOBILE_NBR,

               EMAIL_ADDRESS,

               DRIVERS_LICENSE,

               SOCIAL_SEC_NBR)

       VALUES (T.NAME,

               T.DATE_OF_BIRTH,

               T.HOME_ADDRESS,

              T.HOME_PHONE_NBR,

               T.MOBILE_NBR,

               T.EMAIL_ADDRESS,

               T.DRIVERS_LICENSE,

               T.SOCIAL_SEC_NBR);

If you want to play around with it a bit, the downloadable source code for this chapter at https://www.mc-store.com/products/sql-for-ibm-i-a-database-modernization-guide contains all the necessary statements for creating and populating the temporary table with data that you can then use to test the MERGE statement I just explained. I should also mention that there’s a bit more to the MERGE statement than what I said here. For instance, when you use multiple WHEN MATCHED instructions, the evaluation is from top to bottom and only a match per origin record is allowed. If you want to use a more complex MERGE statement, consult the DB2 for i SQL Reference manual and read the rules carefully. If you stick to simple statements, like the one above, you should be fine with what I explained here.

Rafael Victoria-Pereira

Rafael Victória-Pereira has more than 20 years of IBM i experience as a programmer, analyst, and manager. Over that period, he has been an active voice in the IBM i community, encouraging and helping programmers transition to ILE and free-format RPG. Rafael has written more than 100 technical articles about topics ranging from interfaces (the topic for his first book, Flexible Input, Dazzling Output with IBM i) to modern RPG and SQL in his popular RPG Academy and SQL 101 series on mcpressonline.com and in his books Evolve Your RPG Coding and SQL for IBM i: A Database Modernization Guide. Rafael writes in an easy-to-read, practical style that is highly popular with his audience of IBM technology professionals.

Rafael is the Deputy IT Director - Infrastructures and Services at the Luis Simões Group in Portugal. His areas of expertise include programming in the IBM i native languages (RPG, CL, and DB2 SQL) and in "modern" programming languages, such as Java, C#, and Python, as well as project management and consultancy.


MC Press books written by Rafael Victória-Pereira available now on the MC Press Bookstore.

Evolve Your RPG Coding: Move from OPM to ILE...and Beyond Evolve Your RPG Coding: Move from OPM to ILE...and Beyond
Transition to modern RPG programming with this step-by-step guide through ILE and free-format RPG, SQL, and modernization techniques.
List Price $79.95

Now On Sale

Flexible Input, Dazzling Output with IBM i Flexible Input, Dazzling Output with IBM i
Uncover easier, more flexible ways to get data into your system, plus some methods for exporting and presenting the vital business data it contains.
List Price $79.95

Now On Sale

SQL for IBM i: A Database Modernization Guide SQL for IBM i: A Database Modernization Guide
Learn how to use SQL’s capabilities to modernize and enhance your IBM i database.
List Price $79.95

Now On Sale

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: