Linq leaves DB Connection open 2nd time it runs the same Stored Procedure

Question

0.00/5 (No votes)

See more:

Hi all,

I am seeing some very wierd Linq behaviour in my application and was wondering if anyone could explain it. I'm using .Net 3.5 and MSSQL Server 2008

The first time I run the method, the DB connection remains closed. The second time I run it the connection opens and remains open.

Any ideas why?

XML

public List<sp_MySPResult> GetData(Int32 customerID) {
   var result = new List<sp_MYSPResult>();
   try{
      result = (from n in DB.sp_MYSP(customerID)
                select new sp_MYSPResult{
                    Name = n.Name,
                     Surname = n.Surname}
               ).ToList();
   } catch (Exception ex){
      Console.WriteLine(ex.Message);
   }
   return result;
}

Posted 6-Nov-12 1:51am

madtag76

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

onelopez · Answer 1 · 2012-11-08T08:35:00

Perhaps this function is not closing the connection properly

C#

sp_MYSP

There is a chance that on one of the records it fails and throws an exception so then it causes call to end prematurely and therefore not calling the close on the database.
It's always a good idea to have the close for a stream or database connection in a final scope. That way if it fails, the connection / stream is always closed.