We are currently using Entity Framework Extensions to do bulk inserts which works great but I was looking into the possibility of turning some of our SQL tables into memory optimised tables.

Upon doing some regression testing, part of our .NET application failed as under the hood it is using a MERGE statement to bulk insert the data into the database which you you can’t do with memory optimised tables.

Am I right in thinking it uses a MERGE statement under the hood due to includeGraph being true, which is non-negotiable I think, due to inserting a parent object with child objects attached?

_bulkInsertDb.BulkInsert(foo, inlcudeGraph:true);