Where should I instantiate my service class' SqlDatacontext?

Question

I have several service classes that have static methods and offer a service to the rest of my program. Most of these services involve accessing an instance of SqlDataContext (linq2sql).

First I tried instantiating this connection as a static private member per service class. This works, but it also generates a bunch of lock ups, delays and dirty object problems.

Now I went with a private instance that gets instantiated at method level. This works better in terms of lock ups and problems with dirty objects because the scope is smaller and more predictable, but this also generates a bunch of overhead in terms of connection handshakes.

How do you suggest to take on this problem?

Answer 1

Take a look at this article by Rick Strahl - he explains the options and provides a good factory implementation to cope with creating a single request per web context/thread (depending on what you are working in.

Used this in most of the applications I have worked on where we used linq-to-sql and it seemed the right approach!