Home/ Questions/Q 3795722
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T13:07:38+00:00

I have a large inserting job to perform, say 300000 Inserts. If I do

  • 0

I have a large inserting job to perform, say 300000 Inserts.

If I do it the legacy way, I just write a SQL string with blocks of 100 Insert statements, and perform an executeCommand against the DB (each 100 records).

That lends to some 100 inserts per 3 seconds or so.

Now of course there are issue with single quotes and CrLf’s within the inserted values. So rather than writing code to double the single quotes and so on, since I’m lazy I have a go with Linq InsertOnSubmit and one context.SublitChanges each other 100 rows.

And that take some 20x more times than the legacy way!!!

Why?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You’re not using the right tool for the job. LINQ-to-SQL and most other ORMs (at least Entity Framework and NHibernate) are meant for OLTP scenarios, they are not meant for bulk data operations and will perform slowly when used for bulk data operations.

    You should be using SqlBulkCopy.

    • 0