How to dispose Entity Framework record objects after insertion?

Question

I insert a lot of records into an Entity Framework database and don't need them any more after I run .SaveChanges();. Moreover, I actually would like the memory to be released as soon as possible (for new records to be created). I don't keep any variables linking to old records objects but the GC doesn't seem to delete them, so, I think, it is the data context or something else who keeps them alive. How do I dispose them correctly to let GC to free memory they occupy?

is your context in a `using` statement? – BlueChippy Nov 22 '12 at 09:41 — BlueChippy, Nov 22 '12 at 09:41

score 3 · Answer 1 · answered Nov 22 '12 at 09:42

3

This isn't really a problem. Let the GC do its work.
I think, it is the data context or something else who keeps them alive.

Correct. The basic solution is to Dispose the Context as soon and as often as possible.

answered Nov 22 '12 at 09:42

H H

263,252
30
330
514

Well, but I am going to use it again right after. I have to insert millions of records sequentially, do you mean I have to dispose and re-create the database connection that many times? Can't the context be forced to forget about the records inserted? – Ivan Nov 22 '12 at 09:54
1

Disposing a Context is not the same as closing the connection. – H H Nov 22 '12 at 10:04

score 0 · Answer 2 · answered Nov 22 '12 at 09:44

0

Have you tried creating the context in a 'using' statement?

using(var context = new MyContext())
{
    // Do work here .....
}

answered Nov 22 '12 at 09:44

Rui Jarimba

11,166
11
56
86

score 0 · Accepted Answer · edited May 23 '17 at 11:46

SaveChanges() does not release the resources, it just commits the changes to the database.

To release the resources you need to call Dispose() method of the object context. It can be done explicitly by calling .Dispose() method or by putting your code inside the using statement:

using(var ctx = new EntityModel())
{
    // do the inserts
    ctx.SaveChanges();
}

Also, ObjectContext.Dispose() method closes the connection if it was opened by the Entity Framework, otherwise you can run out of the connections...

Here is a similar question: Should Entity Framework Context be Put into Using Statement?

How to dispose Entity Framework record objects after insertion?

3 Answers3