Home/ Questions/Q 676943
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T00:59:04+00:00

I have an application I’m writing in access with a SQL server backend. One

  • 0

I have an application I’m writing in access with a SQL server backend. One of the most heavily used parts is where the users selects an answer to a question, a stored procedure is then fired which sees if an answer has already been given, if it has an UPDATE is executed, if not an INSERT is executed.

This works just fine but now we have upgraded to SQL server 2008 express I was wondering if it would be better/quicker/more efficient to rewrite this SP to use the new MERGE command.

Does anyone have any idea if this is faster than doing a SELECT followed by either an INSERT or UPDATE?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Not worth the effort. Possibly doable, but it will not give you anything noticable.

    MERGE is especially targeting data warehouses where finding out what to insert/update is the tricky part. It allows all operations (insert, update) to be done with ONE set of merges, compared to one for each condition. This makes no real difference in your case.

    I have one database where I am uploading 3-5 million rows into a 300 million row table – there merge improoves my performance by 50% (one table scan instead of two).

    • 0