Bulk Insert


INSERT all entities in the database.

All entities are considered as new rows and are INSERTED in the database.


// Easy to use

// Easy to customize
context.BulkInsert(list, options => options.BatchSize = 100);


Inserting thousand of entities for an initial load or a file importation is a typical scenario.

SaveChanges methods make quite impossible to handle this kind of situation directly from Entity Framework due to the number of database round-trips required.

SaveChanges require one database round-trip for every entity to insert. So if you need to insert 10000 entities, then 10000 database round-trip will be performed which is INSANELY slow.

BulkInsert in counterpart require the minimum database round-trip as possible. By example under the hood for SQL Server, a simpleSqlBulkCopy could be performed.

Performance Comparisons

Operations 1,000 Entities 2,000 Entities 5,000 Entities
SaveChanges 1,000 ms 2,000 ms 5,000 ms
BulkInsert 6 ms 10 ms 15 ms


How can I specify more than one option?

You can specify more than one option using anonymous block.


context.BulkInsert(list, options => {
	options.BatchSize = 100);
	options.ColumnInputExpression = c => new {c.Name, c.Description});

How can I specify the Batch Size?

You can specify a custom batch size using the BatchSize option.

Read more: BatchSize


context.BulkInsert(list, options => options.BatchSize = 100);

How can I specify custom columns to Insert?

You can specify custom columns using the ColumnInputExpression option.

Read more: ColumnInputExpression


context.BulkInsert(list, options => options.ColumnInputExpression = c => new {c.Name, c.Description});

How can I include child entities (Entity Graph)?

You can include child entities using the IncludeGraph option. Make sure to read about the IncludeGraph since this option is not as trivial as others.

Read more: IncludeGraph


context.BulkInsert(list, options => options.IncludeGraph = true);

Why BulkInsert doesn’t use the ChangeTracker?

To provide the best performance as possible!

Since using the ChangeTracker can greatly reduce performance, we choose to let BulkSaveChanges method to handle scenario with ChangeTracker and BulkInsert scenario without it.

Why BulkInsert is faster than BulkSaveChanges?

The major difference between both methods is BulkSaveChanges use the ChangeTracker but not the BulkInsert method.

By skipping the ChangeTracker, some methods like Add, AddRange, DetectChanges are no longer required which greatly helps to improve the performance.