SQL Server 2005 has a startup check that fails on some of the newer CPU socket designs (triple core, tri core, 12 core, …) as outlined in the knowledge base article: http://support.microsoft.com/kb/954835 Continued testing shows that the NUMPROCS workaround