Under the SQL Server Properties (Right click on Server then Properties) go
to the Connections tab.
By default the Maximum concurrent user connections is set to 0 (unlimited).
You can try setting this to a certain number of connection that you think
will suffice.

Steve S.
[Email Address Removed] 338-1808 x301

-----Original Message-----
From: Kevin Christopher [mailto:Kevin.[Email Address Removed]
Sent: Wednesday, April 28, 2004 03:44 PM
To: LazyDBA.com Discussion
Subject: Limiting an ill-behaved application



I've got an ill-behaved multi-threaded application that opens
several hundred database connections to an MSSQL2000 server, and then issues
queries to the point that the CPU is pegged at 100% (and eventually port
1433 cracks....it looks similar to a Denial-of-Service attack :-()

While I convince the application developers to do better
application-to-database thread management, is there any way I can
unilaterally limit the number of database connections that my Server will
allow from a given user or IP address?

thanks for your help!




---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY Get today's
cartoon: http://www.LazyDBA.com To unsubscribe, e-mail:
mssqldba-[Email Address Removed] , then respond to the confirmation email
you get For additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page