You can certainly limit the maximum number of concurrent connections.
But you're going to get users who can't connect until you kill the
unused ones.
You would certainly want to alert after you reached the maximum, or near
maximum, connections reached.
Anthony Thomas, MCDBA, MCSA
-----Original Message-----
From: Rajendra Mohanty
[mailto:mssqldba-ezmlmshield-x50482346.[Email address protected]
Sent: Wednesday, August 25, 2004 8:34 AM
To: LazyDBA Discussion
Subject: RE: Serious Problem
Hi Adam,
Thanks a ton for your kind suggestion.....
We know the there were no connection release after get connected to the
DB.... But thing is that this application is already live on our live
server.... as this application is used as a MIS tools.... so in a single
time there might be 3-5 concurrent users..... but in future it might be
increased.....Developers are working on it for a permanent
solution.....for the time being does there any solution to restrict the
process upto certain limit.....or the system fire some alert kind of
thing.
Thanks a lot.......
R Mohanty
DBA
Netcradle Ltd.
-----Original Message-----
From: Adam Albina
[mailto:mssqldba-ezmlmshield-x51456674.[Email address protected]
Sent: Wednesday, August 25, 2004 6:26 PM
To: LazyDBA Discussion
Subject: RE: Serious Problem
This is a bit more severe than "connection management on the application
level was not done properly". This is an application developer who
needs some schooling. I'm afraid there is nothing global you can do
from the backend - the problem is with the front end. This application
needs to be re-written to use connection caching and connection pooling.
Most ADO or OLEDB implementations do this for the developer - so it
should be fairly easy for them to implement if they can read up on it a
bit. I can't imagine an application - even a multi-threaded complex
financial application that needs 90 threads with 90 connections to the
database. Imagine trying to keep all those threads synchronized...
It's often a good idea to have a development SQL Server so that these
things can be discovered early on in the development cycle when it's
much easier and less costly to modify the application design.
Best of luck - my recommendation would be to deny the application use of
the server. Many production databases use an application authentication
scheme to make sure that only authorized applications can access the
DBMS.
Adam
Adam R. Albina
Director of Information Technology
Saint Anselm College
100 Saint Anselm Drive, P.O. Box 1711
Manchester, NH 03102
[Email address protected]
603.641.7266 603.801.9587(Mobile) 603.641.7288(Fax)
-----Original Message-----
From: Rajendra Mohanty
[mailto:mssqldba-ezmlmshield-x34576464.[Email address protected]
Sent: Wednesday, August 25, 2004 7:52 AM
To: LazyDBA Discussion
Subject: RE: Serious Problem
Hi,
In one of my application JBO(Juniors Backoffice), whenever any user
login onto the application there are 90 process are open and it was
found that the connection management on the application level was not
done efficiently. Now the problem is if 10 users are login onto the
system than there are 900 processes are open in the system and these
processes are laying in the system unless until the user logout from the
system. The time comes when the maximum limit of the process reaches,
there might be the chances of crashing the system.
Is there any ways to manage this situation from Backend.
Thanks to all.
R Mohanty
DBA
Netcradle Ltd.
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY Website :
http://www.LazyDBA.com To unsubscribe:
http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY Website :
http://www.LazyDBA.com To unsubscribe:
http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]
***********************************************************************
NOTICE: This electronic mail message and any attached files are
confidential. The information is exclusively for the use of the
individual or entity intended as the recipient. If you are not the
intended recipient, any use, copying, printing, reviewing, retention,
disclosure, distribution or forwarding of the message or any attached
file is not authorized and is strictly prohibited. If you have received
this electronic mail message in error, please advise the sender by reply
electronic mail immediately and permanently delete the original
transmission, any attachments and any copies of this message from your
computer system.
***********************************************************************
MS Sql Server LazyDBA home page