>Using SPROCs: That's not going to happen. People here will not permit us to use SPROCs even when I've made a case to use them instead of very complicated LINQ.
>
>Also, SQL Profiler shows that the SQL generated by EF 6.02 or whatever is the latest is not using Merge. It's using either an Insert or an Update.


What's the reason for not permitting sprocs?

SQL Server itself executes system stored procs all the time for different database operations. Does your employer block SQL Server system stored procs? :)

Your employer doesn't seem to have a problem with EF generating SQL code that you really can't adjust (at least not without some very intricate workarounds).

I realize you're working under constraints and might not have any power to change them. But the EF is not the "end all".