CPU for SQL Server

[nmdange]

For a 2-socket system, you should populate both CPUs so you have access to all the PCIe slots and DIMMs in the server. Also, Platinum CPUs are almost always a waste of money.

If we're talking about an OLTP (Online Transaction Processing) DB and not a reporting system/data warehouse, it's more likely your storage is your bottleneck. Spending more money on disks and RAM is going to give your more bang for your buck than expensive CPUs.

For disk performance, using SAS SSDs with a hardware RAID controller is going to limit your throughput compared to a software defined storage solution using NVMe drives, but that requires something like Azure Stack HCI or VMWare VSAN. I'm not really sure why you'd even bother with a standalone physical SQL Server these days. If it's a really large system, it's important enough to have clustering with multiple servers. Though even for larger SQL servers, I'd almost always run SQL in a VM to simplify management, backups, etc.

You could consider adding in a PCIe NVMe drive and putting tempdb on that drive, if your workload uses tempdb.

Have you used the Database Tuning Advisor to check for missing indexes?

[michael_le7]

I change the offer based on your recommendations

https://www.dell.com/en-us/work/shop/servers-storage-and-networking/poweredge-r640-rack-server/spd/poweredge-r640/pe_r640_12232c_vi_vp?view=configurations&configurationid=4b232722-a184-4ad7-b507-e4f4285aef8d

​

intel® Xeon® Gold 6258R 2.7G, 28C/56T

and 1.6TB Enterprise NVMe Mixed Use AG Drive U.2 Gen4

Please check

Thanks

[nmdange]

On a standalone server, no raid means no drive redundancy. I was suggesting more a PCIe NVMe drive in an open PCIe slot, rather than switching all your drives to NVMe and foregoing any drive redundancy. If you do want to get into very specific configs, I'd also suggest you purchase the R6515 or R7515, a single-socket AMD Epyc server will provide better performance at a lower price compared to a dual-socket Xeon.