I recently read a white paper on the performance of Lawson S3 Enterprise Management System running on SQL Server 2008 and was struck by the idleness of SQL Server in handling the type of load seen with large corporations. The SQL Server hardware used was approaching prosumer levels:
- 2 x Quad Code Processors (8 cores)
- 10 GB RAM
- Microsoft Windows Server 2008 R2 64-bit OS
- Microsoft SQL Server 2008 64-bit
Two common measures of SQL Server activity levels are:
- SQL Server CPU Idle Time %
- SQL Server Disk Idle Time %
The worst case was 88% and 95% as shown in the figures below.
How would you describe this amount of idleness? I describe it as napping!
On a practical level it means that the hardware investment may be shared with other applications easily, reducing the total cost of ownership (TCO). This type of result suggests that it is a good candidate for putting on Hyper-V virtual machines, again, reducing TCO.
For more information and additional benefits of using SQL Server 2008 for Lawson's S3 Enterprise Management System, see the whitepaper.