Re: Connection Pooling
From: William Ryan eMVP (dotnetguru_at_comcast.nospam.net)
Date: 04/30/04
- Next message: William Ryan eMVP: "Re: Sttopid Q 2"
- Previous message: JLW: "Re: SELECT .... LIKE doesn't work"
- In reply to: John: "Connection Pooling"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 30 Apr 2004 09:03:21 -0400
It might be. One option is to turn off connection pooling for this piece of
the app. Since all connections have to be killed anyway, you can do
something like this
http://www.knowdotnet.com/articles/killallconnections.html to kill all the
active connections. then you'll know for sure if it's your app or not and
if it is, turn off pooling temporarily...
HTH,
Bill
"John" <anonymous@discussions.microsoft.com> wrote in message
news:CD9C3DBE-570B-4F76-AD82-0A334C427193@microsoft.com...
>
> Hi All,
>
> I have a single-threaded WinForms app which uses SQL Server 2000 as its
database.
> Part of the app is a 'Restore from Backup' form which uses SQLDMO code. I
keep getting
> errors telling me that there are other connections open - therefore the
restore can't go ahead.
> I used sp_who to check connections during code step-through and it's true.
However, any
> connections made in the app have been closed at that stage.
>
> I'm starting to think it's to do with connection pooling because the open
connection(s) disappear
> when the app closes. I've looked around for code examples to implement
some of the
> key/value properties for ConnectionStrings, but this has been fruitless.
>
> Has anyone got any other ideas?
>
> Thanks!
>
> John
>
>
>
>
>
- Next message: William Ryan eMVP: "Re: Sttopid Q 2"
- Previous message: JLW: "Re: SELECT .... LIKE doesn't work"
- In reply to: John: "Connection Pooling"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
