I'd would add though that the original issue I encountered should be a bug.

Thanks to all those who responded to this topic. 😎

edited. double post.

actually it does. If you "select * into <copy> from <source>", which is basically what I did to create the output table, you'll find that the same columns that are...

OK, so i went back to try setting identity_insert on LocDisplay instead of the output table. I was worried that the merge would fail in the INSERT section... but it...

Thanks for the reply, Nick.

That IS the message I am getting with the above statement, and that's just the thing, it's complaining about the target table (INSERT) LocDisplay and not...

So far, the solution for my particular problem is to simply convert the identity column in the OUTPUT table to a non-identity one.

It's a pain if I have to do...

I even tried this one but I get the same error.

select distinct SomeCode, PlaneCode into #t from LocDisplay

set identity_insert LocDisplay_merge_output_20160902 on;

insert into LocDisplay(LocCode, LocName, SomeCode, PlaneCode)

output 'INSERT', inserted.LocId, inserted.LocCode, inserted.LocName,...