Entity Framework Classic Batch SaveChanges

Description

The Batch SaveChanges feature allows you to reduce the number of database round-trips by internally batching multiple commands in the same command when saving your entities.

// context.SaveChanges();    
context.BatchSaveChanges();

Try it: NET Core | NET Framework

HINT:

We recommend to always use BatchSaveChanges over SaveChanges or enable the option UseBatchForSaveChanges.

Performance Comparison

Try it: NET Core | NET Framework

HINT:

Performance may differ from a database to another. A lot of factors might affect the benchmark time such as index, column type, latency, throttling, etc.

Why BatchSaveChanges is faster than SaveChanges?

For both methods, the same SQL Syntax to perform the save operation is used.

So if you have 10 rows to insert:

• SaveChanges: Will execute one database round-trip for every row. So 10 database round-trips will be performed.
• BatchSaveChanges: Will batch all SQL in one command and will perform one database round-trip. So, one database round-trip will be performed.

Getting Started

Use BatchSaveChanges

// context.SaveChanges();    
context.BatchSaveChanges();

Try it: NET Core | NET Framework

Internally replace SaveChanges by BatchSaveChanges

public class EntityContext : DbContext
{
    public EntityContext() : base(FiddleHelper.GetConnectionStringSqlServer())
    {
        this.Configuration.BatchSaveChanges.UseBatchForSaveChanges = true;
    }
    
    public DbSet<Customer> Customers { get; set; }
}

context.Customers.AddRange(customers);
context.SaveChanges();

Try it: NET Core | NET Framework

Documentation

Properties

Methods

Limitations

• All providers that don't support multi statements such as SQL Compact and Effort will automatically use SaveChanges instead.