What could cause left open SQL data connection

[Paul]

Hi just wondering what could cause a left open SQL connection as this has only occured 2 times in the last week. The error it creates is when a web app tries to open a connection an error message states, it is already open. The process was then killed to close the connection. The usage is pretty low around 15 workstations. Looking at the code it appears that all connections get closed, so thinking it is not a problem with the code. Thanks Paul.

[Scott M.]

Are you calling the .close method of the connection or just killing the
process? Killing the process won't close the ADO.NET SQLConnection object.

You should have your .open method in a Try...Catch and the .close method in
the Finally.
"Paul" <an*******@disc ussions.microso ft.com> wrote in message
news:5A******** *************** ***********@mic rosoft.com...

Hi just wondering what could cause a left open SQL connection as this has

only occured 2 times in the last week. The error it creates is when a web
app tries to open a connection an error message states, it is already open.
The process was then killed to close the connection. The usage is pretty
low around 15 workstations. Looking at the code it appears that all
connections get closed, so thinking it is not a problem with the code.
Thanks Paul.

[William Ryan eMVP]

Paul...

if you have this code
myConnection.Op en();
int i = myCommand.Execu teScalar();
myConnection.Cl ose
and you raise an exception, you'll never hit close so I'd check that first,
and move my close statements to Finally blocks. I'm guessing that's the
problem. If not, let me know.

Bill
"Paul" <an*******@disc ussions.microso ft.com> wrote in message
news:5A******** *************** ***********@mic rosoft.com...

Hi just wondering what could cause a left open SQL connection as this has

only occured 2 times in the last week. The error it creates is when a web
app tries to open a connection an error message states, it is already open.
The process was then killed to close the connection. The usage is pretty
low around 15 workstations. Looking at the code it appears that all
connections get closed, so thinking it is not a problem with the code.
Thanks Paul.

[Kevin Spencer]

It's definitely a problem with the code. It sounds like some developer is
playing around with re-using Connections in your app. Not a good practice in
..Net.

General rule of thumb: Open a Connection when you need it, use it, Close it
as soon as you're done with it.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Paul" <an*******@disc ussions.microso ft.com> wrote in message
news:5A******** *************** ***********@mic rosoft.com...

Hi just wondering what could cause a left open SQL connection as this has

only occured 2 times in the last week. The error it creates is when a web
app tries to open a connection an error message states, it is already open.
The process was then killed to close the connection. The usage is pretty
low around 15 workstations. Looking at the code it appears that all
connections get closed, so thinking it is not a problem with the code.
Thanks Paul.

[Kevin Spencer]

Didn't think of that! Excellent suggestion!

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"William Ryan eMVP" <do********@com cast.nospam.net > wrote in message
news:e$******** ******@TK2MSFTN GP09.phx.gbl...

Paul...

if you have this code
myConnection.Op en();
int i = myCommand.Execu teScalar();
myConnection.Cl ose
and you raise an exception, you'll never hit close so I'd check that first, and move my close statements to Finally blocks. I'm guessing that's the
problem. If not, let me know.

Bill
"Paul" <an*******@disc ussions.microso ft.com> wrote in message
news:5A******** *************** ***********@mic rosoft.com...

Hi just wondering what could cause a left open SQL connection as this

has only occured 2 times in the last week. The error it creates is when a web
app tries to open a connection an error message states, it is already open. The process was then killed to close the connection. The usage is pretty
low around 15 workstations. Looking at the code it appears that all
connections get closed, so thinking it is not a problem with the code.
Thanks Paul.

[Chad Crowder]

Agreed. I read that post and was like, holy cow I need to check my code!

Thanks Bill!

- Chad
"Kevin Spencer" <ke***@takempis .com> wrote in message
news:uX******** ******@TK2MSFTN GP09.phx.gbl...

Didn't think of that! Excellent suggestion!

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"William Ryan eMVP" <do********@com cast.nospam.net > wrote in message
news:e$******** ******@TK2MSFTN GP09.phx.gbl...

Paul...

if you have this code
myConnection.Op en();
int i = myCommand.Execu teScalar();
myConnection.Cl ose
and you raise an exception, you'll never hit close so I'd check that

first,

and move my close statements to Finally blocks. I'm guessing that's the
problem. If not, let me know.

Bill
"Paul" <an*******@disc ussions.microso ft.com> wrote in message
news:5A******** *************** ***********@mic rosoft.com...

Hi just wondering what could cause a left open SQL connection as this has

only occured 2 times in the last week. The error it creates is when a

web app tries to open a connection an error message states, it is already

open.

The process was then killed to close the connection. The usage is pretty low around 15 workstations. Looking at the code it appears that all
connections get closed, so thinking it is not a problem with the code.
Thanks Paul.

[Paul]

ok thanks for the responses. This is code that someone else developed and I have modified
I did add a section of code that uses a data connection, data adapter, and a dataset. It calls a stored procedure on the server. I did not use open or close in the code but it seemed to be working ok. The stored procedure pulls data from a few tables and displays it on the data grid
Do I need to implicitly use the open and close statements for the connection or data adapter for this or does the fill automatically open the connection and then close it

SqlDataAdapter1 .Fill(ds_vhist, "dbo_pg_parmsel _past_reservati on"
Vhistgrid.DataB ind(

Thank
Paul.

[Paul]

ok thanks for the responses. This is code that someone else developed and I have modified
I did add a section of code that uses a data connection, data adapter, and a dataset. It calls a stored procedure on the server. I did not use open or close in the code but it seemed to be working ok. The stored procedure pulls data from a few tables and displays it on the data grid
Do I need to implicitly use the open and close statements for the connection or data adapter for this or does the fill automatically open the connection and then close it

SqlDataAdapter1 .Fill(ds_vhist, "dbo_pg_parmsel _past_reservati on"
Vhistgrid.DataB ind(

Thank
Paul.