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 |
dewacorp.alliances
452 Posts |
Posted - 2006-09-25 : 22:55:57
|
Hi DBAsWe have a baseline for our server and one thing that we notice that for indicator: General Statistics - User Connections: Min: 224 and Max: 417, avg: 278 for 6 hours monitoring.This indicates that we need to increase the Maximum Worker Treads to 450.Question is:1. Is this the right indication using this General Statistics - User Connections to determine the Max Worker Threads?2. Most of the connection they are all sleeping anyway ... is there any way to reduce this connection?3. If we do changing the Max Worker Threads ... do we need restart the SQL service?Thanks |
|
JoeNak
Constraint Violating Yak Guru
292 Posts |
Posted - 2006-09-25 : 23:41:53
|
The number of user connections doesn't correlate to worker threads. Everything that I've read discourages increasing Max Worker Threads from the default (255).Here's a couple of links to check out:http://support.microsoft.com/?kbid=319942http://blogs.msdn.com/khen1234/archive/2005/11/07/489778.aspxNot sure if you're having a specific issue, if so I'd advise posting more (specific) information. Otherwise you might want to take a look at http://www.sql-server-performance.com/. |
 |
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2006-09-26 : 13:52:42
|
I'd probably look at disk utilization before user connections. Most times, the Disk or RAM is the first bottleneck for SQL server.Michael<Yoda>Use the Search page you must. Find the answer you will. Cursors, path to the Dark Side they are. Avoid them, you must. Use Order By NewID() to get a random record you will.</Yoda>Opinions expressed in this post are not necessarily those of TeleVox Software, inc. All information is provided "AS IS" with no warranties and confers no rights. |
 |
|
|
|
|