Windows Server 2008 Std
SQL Server 2005 SP4 64 Bit
2X Intel L5430 2.6 GHZ processors w/ 4 cores each HT enabled
32 Gigs RAM
Storage: Local 1 5 disk RAID 5 (most data), a 2 disk RAID1 (tempdb), and a 2 disk RAID 1 (Logs/system)
Windows Server 2008 R2
SQL Server 2005 SP4 64 bit (tried SQL Server 2008 R2 and 2012 with same results)
4X Intel E7-4830 2.13 GHZ processors w/8 cores each HT not enabled (32 total cores)
132 Gigs RAM
Storage Local 1 10 SSD RAID 5 (data), a 2 SSD RAID 1 (tempdb), and a 2 SSD RAID1 (Logs, system)
I know you need more info but...
I've run lots of tests w/ SQLIO and found the disk system doing well. I've also collected a lot of wait stats data, but unfortunately, nothing significant to report there. I suspect memory or motherboard (FSB), because I do see significant network_async_io waits (300 ms on a 2 sec query) when executing longer queries locally on the new server using SSMS. Since the only protocol used for these queries is Shared Memory, maybe there is something there. Incidentally, I don't see the network_async_io waits when executing the same query from another client.
Any truth to the story that you can have too much memory/processing power for SQL Server?
Any obvious gotchas?
Any help / direction as to how to proceed?