January 26, 2009 at 1:15 pm
For some reason when someone runs a process on the server, it takes almost all the available open processed. Not being a DBA by open processed I mean those that did say AWAITING COMMAND.
Everything else is set as background.
How can this be prevented. After the first user kicks off a procedure all future users processes are slow. Not being blocked but just no available open process.
How many AWAITING COMMAND processed should be configured to start ?
Thanks,
Richard
January 28, 2009 at 9:05 am
Richard, What is "some process" trying to do? I've seen thousands of connections to a server without slowing it down to any noticable degree.
In some cases the front end ( app/web server ) will keep connections open even after the command is complete. Could be something to do with connection pooling at the app server. If your app server is using a service account all you are ever going to see is one account access with hundreds or thousands of spids
_______________________________________________________________________
Work smarter not harder.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply