By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,263 Members | 1,321 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,263 IT Pros & Developers. It's quick & easy.

Running out of Sql Connections

P: n/a
Hello:
We have a a two tier application connecting to sql server
through remoting. The business objects are single call objects. We are
opening and closing connections using ADO.NET command object. All
"ExecuteNonQuery" are closed in finally blocks. We are running out of
sql connections because the profiler shows that connections are not
being released till the business service is stopped and restarted.
Does anyone have suggestions on how to fix this problem of the
connections not closing and why it may be happening?

Thanks a lot,
Han

Jul 23 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi

It is hard to say without seeing code what you are doing, but if you have an
implicit connection then the connection is not returned to the pool.
http://support.microsoft.com/default...b;en-us;191572

Using profiler or performance monitor you should be able to track
connections being used.

This may also happen to use up connections:
http://support.microsoft.com/default...b;en-us;235282

I found this which may be what is happening:
http://msdn.microsoft.com/library/de...singADONET.asp
Note Do not call Close or Dispose on a Connection, a DataReader, or any
other managed object in the Finalize method of your class. In a finalizer,
only release unmanaged resources that your class owns directly. If your
class does not own any unmanaged resources, do not include a Finalize method
in your class definition

John

<ha******@yahoo.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...
Hello:
We have a a two tier application connecting to sql server
through remoting. The business objects are single call objects. We are
opening and closing connections using ADO.NET command object. All
"ExecuteNonQuery" are closed in finally blocks. We are running out of
sql connections because the profiler shows that connections are not
being released till the business service is stopped and restarted.
Does anyone have suggestions on how to fix this problem of the
connections not closing and why it may be happening?

Thanks a lot,
Han

Jul 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.