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 |
kappa02
Yak Posting Veteran
65 Posts |
Posted - 2009-03-10 : 14:29:51
|
How can one user have so many treads specially if they are just idle and not running anything? How can I reduce this because it appears to slow the system down.SPID STATUS login Hostname407 sleeping ASmith ASMITH2008 408 sleeping ASmith ASMITH2008 409 sleeping ASmith ASMITH2008 410 sleeping ASmith ASMITH2008 411 sleeping ASmith ASMITH2008 412 sleeping ASmith ASMITH2008 413 sleeping ASmith ASMITH2008 414 sleeping ASmith ASMITH2008 415 sleeping CCSmith CCSMITH2008 417 sleeping BBSmith BBSMITH08 418 sleeping BBSmith BBSMITH08 419 sleeping BBSmith BBSMITH08 420 sleeping BBSmith BBSMITH08 421 sleeping CCSmith CCSMITH2008 424 sleeping BBSmith BBSMITH08 425 sleeping BBSmith BBSMITH08 426 sleeping BBSmith BBSMITH08 427 sleeping BBSmith BBSMITH08 428 sleeping BBSmith BBSMITH08 430 sleeping BBSmith BBSMITH08 433 sleeping CCSmith CCSMITH2008 435 SUSPENDED CCSmith CCSMITH2008 437 sleeping CCSmith CCSMITH2008 |
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2009-03-10 : 15:08:07
|
You can use the kill command to kill the SPID's you don't want. If this is going to be an issue you might look into a login trigger to limit the # of connections per login name.Mike"oh, that monkey is going to pay" |
 |
|
kappa02
Yak Posting Veteran
65 Posts |
Posted - 2009-03-10 : 15:40:59
|
Yeah, I know that. I wonder why so many off of one user login connection And is there a way to prevent so many for one login. |
 |
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2009-03-10 : 16:10:39
|
I can't answer the why question. The logon trigger would limit the # of connections per login.Mike"oh, that monkey is going to pay" |
 |
|
kappa02
Yak Posting Veteran
65 Posts |
Posted - 2009-03-10 : 16:20:10
|
Where can I find the setting (logon trigger) ? |
 |
|
|
|
|