Closing out database connections. Timeouts

D

Do

Hi,

Is it better to

objConn = Nothing
or
objConn.Close.

I'm starting to get an error message that

Timeout expired. The timeout period elapsed prior to obtaining a connection
from the pool. This may have occurred because all pooled connections were in
use and max pool size was reached.
What am I doing wrong?

Thanks,

Do
 
F

Frank Oquendo

Do said:
Hi,

Is it better to

objConn = Nothing
or
objConn.Close.

objConn.Close(). Database connections do not close themseleves upon
going out scope.
What am I doing wrong?

There are other issues to consider such as network latency and server
load. But start by closing all your connections as soon as you're done
with them and take it from there.

--
There are 10 kinds of people. Those who understand binary and those who
don't.

http://code.acadx.com
(Pull the pin to reply)
 
S

srinivas moorthy

Hi,
Timeout Problem arises if you have any query which
consumes more resources and more time in execution. Just
cross check with the Query which you are using in SQL
QUERY Analyzer.

For the Command Object there is a property called TimeOut
which u can set an integer value for query execution time
period.

Thanks
srinivas moorthy
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,755
Messages
2,569,536
Members
45,014
Latest member
BiancaFix3

Latest Threads

Top