Does anyone know if 1 thread always equals on cpu hit? My company is highly batch intensive, but the jobs running in batch are serialized so that only one job is running at a time. On our 4 processor servers, looking at task manager or any other monitoring tool it appears that we hit only one cpu. When a job finishes and another starts up it cycles to the next cpu. The server registers almost nothing on any other cpu during batch. The server is setup to use all available processors, but it really looks as though throwing additional cpu at my problem is a waste of resources. We are having issues at night getting through our batch window before the system needs to be up in the morning. My network admins want to throw bigger hardware at it, but I am unsure it will fix the solution with what I am seeing via monitoring. I am suprised that SQL Server does not take care of multi-threading to the processors by default, but I find no reference out there on the inner architecture of the database engine nor of tuning to do for this. Any help on things to try would be greatly appreciated.