Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
pie8ter
Starting Member
7 Posts |
 Posted - 2007-05-03 : 17:17:45
|
| SQL 2000/running on Windows 2003 SP1Occasionally, one of the DBs ends up using 100 connections. When this happens, the server runs really slow and I can see the sqlserver process is using more than half the memory. Users accessing other DBs complain that their apps is extremely slow or doesn't respond sometimes. The problem is with the app making the connection. The development team is working on this. My question is how I can kill all these processes. I went to Management->show processes right click on a process and select kill. But it doesn't seem to work. Either the process is trying to rollback the transaction or is crashed? Also, how can I builk kill? Killing 100 processes one by one would be time consuming.Thanks |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-05-03 : 17:32:03
|
| Why do you need to kill these connections? What makes you think that these connections are causing your slowness problem?BTW, SQL Server typically uses way more than half the memory. This is normal. Do not reboot SQL Server to reclaim it. SQL Server is designed to be memory hog. This is why SQL Server should be on a dedicated server.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-05-03 : 23:30:15
|
| What's total db size and amount of memory on the server? May need more memory. |
|
|
|
|
|
|
Killing sleeping and unresponsive processes