How to close connection pool?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Let me say preemptively I've read up on this and searched postings here and
haven't found an answer.

Connection pooling doesn't provide a way to close all connections in the
pool, short of exiting the process. This seems to me to be a designed-in
leak. I can think of a few scenarios where this creates an administrative
problem, one of which I'm in.

Thanks.
 
The feature is added in .net 2 for oracle and sqlserver.
Why is this (an administrative) problem for you?
 
Just seems like a major design hiccup not to be able to control that. The
scenarios are unlimited. In my case, I want to perform a restore on a
database from the application. If that database has ever been accessed from
the application, then there will be effectively orphaned connections in the
pool preventing it until the user exits the application. We dodged a bullet
in that the action is normally only performed when the application is first
started. However, some configuration information gets loaded from the DB
before that, so I need to set pooling to false for that action. So, I have
workarounds in my case, but still seems odd not to be able to control it.

Miha Markic said:
The feature is added in .net 2 for oracle and sqlserver.
Why is this (an administrative) problem for you?

--
Miha Markic [MVP C#]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

pearsons_11114 said:
Let me say preemptively I've read up on this and searched postings here
and
haven't found an answer.

Connection pooling doesn't provide a way to close all connections in the
pool, short of exiting the process. This seems to me to be a designed-in
leak. I can think of a few scenarios where this creates an administrative
problem, one of which I'm in.

Thanks.
Click to expand...
Click to expand...
 
I see. I guess what are you doing is the only thing you can do.
Perhaps you might consider going in single use mode (thus drop all exisitng
connections) before doing restore?

--
Miha Markic [MVP C#]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

pearsons_11114 said:
Just seems like a major design hiccup not to be able to control that. The
scenarios are unlimited. In my case, I want to perform a restore on a
database from the application. If that database has ever been accessed
from
the application, then there will be effectively orphaned connections in
the
pool preventing it until the user exits the application. We dodged a
bullet
in that the action is normally only performed when the application is
first
started. However, some configuration information gets loaded from the DB
before that, so I need to set pooling to false for that action. So, I have
workarounds in my case, but still seems odd not to be able to control it.

Miha Markic said:
The feature is added in .net 2 for oracle and sqlserver.
Why is this (an administrative) problem for you?

--
Miha Markic [MVP C#]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

message
Let me say preemptively I've read up on this and searched postings here
and
haven't found an answer.

Connection pooling doesn't provide a way to close all connections in
the
pool, short of exiting the process. This seems to me to be a
designed-in
leak. I can think of a few scenarios where this creates an
administrative
problem, one of which I'm in.

Thanks.
Click to expand...
Click to expand...
Click to expand...
 
Duh. My rusty DBA skills exposed. That does the trick. Thanks!

Miha Markic said:
I see. I guess what are you doing is the only thing you can do.
Perhaps you might consider going in single use mode (thus drop all exisitng
connections) before doing restore?

--
Miha Markic [MVP C#]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

pearsons_11114 said:
Just seems like a major design hiccup not to be able to control that. The
scenarios are unlimited. In my case, I want to perform a restore on a
database from the application. If that database has ever been accessed
from
the application, then there will be effectively orphaned connections in
the
pool preventing it until the user exits the application. We dodged a
bullet
in that the action is normally only performed when the application is
first
started. However, some configuration information gets loaded from the DB
before that, so I need to set pooling to false for that action. So, I have
workarounds in my case, but still seems odd not to be able to control it.

Miha Markic said:
The feature is added in .net 2 for oracle and sqlserver.
Why is this (an administrative) problem for you?

--
Miha Markic [MVP C#]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

message
Let me say preemptively I've read up on this and searched postings here
and
haven't found an answer.

Connection pooling doesn't provide a way to close all connections in
the
pool, short of exiting the process. This seems to me to be a
designed-in
leak. I can think of a few scenarios where this creates an
administrative
problem, one of which I'm in.

Thanks.
Click to expand...
Click to expand...
Click to expand...
 
Simply open connections with pooling disabled--or as suggested when
performing maintenance, use single-user mode.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

pearsons_11114 said:
Just seems like a major design hiccup not to be able to control that. The
scenarios are unlimited. In my case, I want to perform a restore on a
database from the application. If that database has ever been accessed
from
the application, then there will be effectively orphaned connections in
the
pool preventing it until the user exits the application. We dodged a
bullet
in that the action is normally only performed when the application is
first
started. However, some configuration information gets loaded from the DB
before that, so I need to set pooling to false for that action. So, I have
workarounds in my case, but still seems odd not to be able to control it.

Miha Markic said:
The feature is added in .net 2 for oracle and sqlserver.
Why is this (an administrative) problem for you?

--
Miha Markic [MVP C#]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

message
Let me say preemptively I've read up on this and searched postings here
and
haven't found an answer.

Connection pooling doesn't provide a way to close all connections in
the
pool, short of exiting the process. This seems to me to be a
designed-in
leak. I can think of a few scenarios where this creates an
administrative
problem, one of which I'm in.

Thanks.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top