August 27, 2004 at 1:12 pm
In an experiment to try to improve server performance, we recently changed our SQL server (SQL2000 enterprise) to have SQL only use 3 of the machine's 4 CPU's, (leaving a CPU available for the OS). Since we made the change, I have noticed that whenever I run SQL profiler, the CPU column seems to contain bogus data. Most of the time it is 0, the rest of the time it seems to be one of a small set of large arbitrary numbers. For example, in today's trace, every query had a CPU reading of 0, 19250, 22313 or 32953.
Firstly, is segregating CPU's a good or bad idea? Secondly, how do I fix the CPU reading?
September 7, 2004 at 8:00 am
Multiple CPU benefits depend on your application. Keep in mind that for licensing MS requires 1 license per processor (physical processor, not logical as case with hyperthreading). In some cases if you get slower execution because of parallel execution plans you can use the MAXDOP=1 option on a per query basis.
I'm not sure what is going on with your CPU reading. Maybe try posting to the performance forum.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy