Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've a question about the merge performance in oracle. I work in the business intelligence area of a big company and its quite common to have to move millions of records one side to other.

The other day my DBA told me the following:

Take a look at this, MERGE statement cold be more elegant but it provokes big problems in performance.

I'm not an expert in this, but it doesn't make sense to me. And looking in the date of the publication of the article (December, 2008) looks like in could be out of date.

We work in Oracle 11g

Should I rewrite my procedures to avoid MERGE? Thanks!

share|improve this question
Never, ever, read anything from that website. I won't say any more, as he's known to sue – Phil Mar 13 '14 at 10:40
sorry for my ignorance, but it has a bad reputation or something? – Lucas Mar 13 '14 at 10:43
"Should I rewrite my procedures to avoid MERGE?" - do you have performance problems related to the merge? If no, then no. If yes, then test alternatives, and if alternatives run better, then use those. – Mat Mar 13 '14 at 12:18
Do you HAVE a performance problem that can be attributed MERGE statement? Then yes, go ahead. Do you really need a MERGE? I see developers use MERGE where all they do is UPDATE or INSERT. MERGE is more suitable when you need to do more than just insert or update etc as part of same action. Since it is more complicated than a simple insert/update there may be little impact but you can always test and verify. – Raj Mar 18 '14 at 13:08

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.