|
|
Posted by Joe Cool on 06/01/05 23:23
On Wed, 1 Jun 2005 13:49:16 -0400, "Marina" <someone@nospam.com>
wrote:
>This is called connection pooling. It is a good thing, why would you want to
>get rid of it?
>
>"Joe Cool" <joecool@home.net> wrote in message
>news:qjqr911o1pun4psdtkn7j76ncs0a3n5j4b@4ax.com...
>> As most of you are aware, when you close a VB.NET connectrion to a SQL
>> server, the connection doesn't actually drop right then and there.
>> From my tests, using VB.NET 2003 and SQL2K, the connection doesn't
>> timeout and drop off for 6 1/2 minutes. How can one force this
>> connection to immediately drop off with code?
>>
>
As you and others have asked "Why?" here's the answer. I am developing
a VB.NET application that uses SQL as the database backend and I check
the existance of all required tables when the application starts. If
any tables are missing, I assume the database is corrupt and give the
user the option of deleting the current corrupt database and
recreating it. I open a connection to scan the database for the
requied tables and iof the user wants to start over, I would like to
close the connection and immediately open a connection to the master
database and drop the application database. But with connection
pooling, it appears that I will have to wait for 6 1/2 minutes (in my
case) before I can do that. I would prefer to not have to wait.
Yes, connection pooling is a good thing, but I would like to
temporarily disable it in this case.
Navigation:
[Reply to this message]
|