quick linq-to-sql what would be more efficient.

Question

What is the life cycle of a data context.

MyDB_DataContext db = new MyDB_DataContext();

Is it more efficient to pass one context across several methods or create new instances of it. OR is there any reason to choose one over the other

public void DoStuff(){
    MyDB_DataContext db = new MyDB_DataContext();
    doMoreStuff()
}
private void doMoreStuff(){
    MyDB_DataContext db = new MyDB_DataContext();
    return;
}

VS

public void DoStuff(){
    MyDB_DataContext db = new MyDB_DataContext();
    doMoreStuff(db)
}
private void doMoreStuff(MyDB_DataContext db){            
    return;
}

Answer 1

There's no hard-and-fast rules, but to give you some context, DataContexts should generally be per-request if you're writing a website. Don't create it all the time, but what you definitely don't want to do is carry around the DataContext as a singleton.

Edit: %s/session/request/g

Answer 2

Hi Kieran,

well in my opinion you can use one instance in all method because everytime when you call instance new method the memory get refresh and your instances get new value without effecting your recent value.well datacontext is only used to make object for dataclasses so that we can easily call any table or stored procedure in any method.

As you can declare datacontext as a global variable.its one object works fine for all methods.