We have SQL Server 2008 Standard licensed for a single processor. We wish to install it on our VMWare platform. Obviously we intend limit the virtual machine to one virtual processor in order to comply with the licence.
As we understand it, a virtual processor is never distributed over more than one physical processor, but will have access to multiple cores on the single processor. If so, that sounds ideal both for performance and for complying with the licence. However...
The potential problem is that our SQL guru insists that SQL Server needs to be able to see that the CPU has 4 cores in order for it to allocate the work efficiently. VMWare does not seem to do this. It presents the virtual CPU as having one core and presumably manages the physical cores itself, transparently to SQL Server.
Is this really a problem? Does it matter that SQL Server can't see the cores and manage them itself? Will this really impact performance, or will VMWare manage the workload across the cores just as efficiently as SQL Server would on a physical server?
If it is going to affect performance, then how do we work around this?
It sounds like we probably need to provide SQL Server with one virtual processor that has distinct virtual cores (which may or may not have any relationship to the physical cores) in a way that the scheduler can use bu
View Complete Post