Prev: Help on simple SQL statement
Next: SQL Agent CmdExec step and environment variables
From: fniles on 11 May 2010 20:29
I am using SQL 2005.
Starting from today, when I do sp_who, every few minutes I see a new
connection to the database and the status is "suspended".
This new connection comes from the same VB.NET program that inserts data to
the database.
After a while, the program will get the error
"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 does the status "suspended" mean, and will it use up all the connection
from the pool ?
How can I fix this ?

Thank you


From: fniles on 11 May 2010 21:40
Looks like COMMIT TRANSACTION fixed the problem.


"fniles" <fniles(a)pfmail.com> wrote in message
news:unH%230oW8KHA.5848(a)TK2MSFTNGP06.phx.gbl...
>I am using SQL 2005.
> Starting from today, when I do sp_who, every few minutes I see a new
> connection to the database and the status is "suspended".
> This new connection comes from the same VB.NET program that inserts data
> to the database.
> After a while, the program will get the error
> "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 does the status "suspended" mean, and will it use up all the
> connection from the pool ?
> How can I fix this ?
>
> Thank you
>


From: Cor Ligthert[MVP] on 12 May 2010 03:51


"fniles" <fniles(a)pfmail.com> wrote in message
news:erkUGQX8KHA.5848(a)TK2MSFTNGP06.phx.gbl...
> Looks like COMMIT TRANSACTION fixed the problem.
>
Or Rollback Transaction

http://msdn.microsoft.com/en-us/library/ms181299.aspx


 | 
Pages: 1
Prev: Help on simple SQL statement
Next: SQL Agent CmdExec step and environment variables