Dual Processors - Testing performance

[GJP55]

We are currently reviewing our licensing options for SQL and have SQL Server running on a dual processor Server.

Is there a way we can test the performance of running with just one processor and then compare it against when both are running ?

 

[jgoodman00]

I have never found an easy way of doing this (& would love to find one).

http://www.quest.com/benchmark_factory/

You might be able to get some answers from this program, but I have had limited success with it...

James Goodman MCSE, MCDBA

http://www.angelfire.com/sports/f1pictures

 

[mrdenny]

Closest thing you could do is tell the SQL Server to only use one processor, but then everything running on the server will still have access to the second processor.

The best way would be to remove the second processor and test, then replace it.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[jgoodman00]

The best way would be to remove the second processor and test, then replace it.

Is this possible though?

You have to ugrade the drivers to support multi-processors. These drivers do not support single-processor usage...

James Goodman MCSE, MCDBA

http://www.angelfire.com/sports/f1pictures

 

[GJP55]

I think we will just stay as we are and go for 2 processor licenses rather than risk messing up the server. It doesn't look like we would get clear cut measures by doing this.

Thanks for both replies.

 

[octothorpe]

Actually, the process is simple. Open SQL Server Enterprise Manager, and in your SQL Server group, right-click the server you want to test and click properties.

There should be a 'Processor' tab. The first section governs which processors SQL Server will use. Just un-check one of the processors.

Optionally, you can physically remove one of the processors (or disable it in the BIOS if the option is there). HAL will not complain on most SMP mainboards -- the system just runs "gracefully degraded". Just be sure to remove power from the system before pulling a CPU (and before putting it back in).

Physically pulling the CPU is naturally more risky than just telling SQL Server to use only one processor -- but also more accurate. Another option is to load SQL Server on a single-processor system to test it.

 

[GJP55]

Thanks for that. Not going to bother with the removal of the processor now but will try the EM steps. Thanks