mutley1
MIS
- Jul 24, 2003
- 909
Hope you all had a very merry Xmas!!
SQL 2000
Just looking through the wait types and blocking from sysprocesses in master and for a few processes, it regularly turns up with CXPACKET as the waittype. We frequently have between 250 - 350 connections to the SQL server, and CPU usage for SQL is usually running between 5 and 50% throughout the day, spiking occasionally.
I have been reading up on MAX WORKER THREADS option, as ours is currently set to 255. Some sites say it is a good option to change, some say it is a bad idea.
Question is, given the above, what else do I need to check to see if changing the MAX WORKER THREADS option to, say 300, would possibly be detremental to the system? Or should I not even consider doing that?
It's an 8 CPU machine and max degree of parallelism is currently set to 3 CPUs.
TIA,
M.
SQL 2000
Just looking through the wait types and blocking from sysprocesses in master and for a few processes, it regularly turns up with CXPACKET as the waittype. We frequently have between 250 - 350 connections to the SQL server, and CPU usage for SQL is usually running between 5 and 50% throughout the day, spiking occasionally.
I have been reading up on MAX WORKER THREADS option, as ours is currently set to 255. Some sites say it is a good option to change, some say it is a bad idea.
Question is, given the above, what else do I need to check to see if changing the MAX WORKER THREADS option to, say 300, would possibly be detremental to the system? Or should I not even consider doing that?
It's an 8 CPU machine and max degree of parallelism is currently set to 3 CPUs.
TIA,
M.