gopher_49
asked on
SQL 2005 process running at 100% CPU
My sqlservr.exe process is running at 100% CPU utilization throughout most of the day... I'm running Windows 2003 Server 32 bit as a VM on a VMWare ESXi host. I found the below link, however, I'm not sure if I'm running NUMA (non-uniform memory access). Does this hotfix pertain to me? The ESXi host hardward is a HP DL 380 G4.
http://support.microsoft.com/kb/931821/en-us
http://support.microsoft.com/kb/931821/en-us
Danny McDaniel
it doesn't appear that your system is supported by ESXi 4.x and doesn't have the newer Intel processors that are NUMA based, so unless you see the lazywriter behavior described in the MS KB...I would think that it doesn't apply to you and your cause is something else.
ASKER
ok.. I might simply be that I have alot of indexing and/or transactions going on. It's constantly archiving emails. Once I stop the archiving process (on a different server) it then gets better... What if I set the priority to the process lower? Would that help? Is that suggested?
I'm not a SQL expert so I don't know what the affect would be if you changed the process priority. You might want to open this question up to the SQL Server zone.
Hi
With this server and this CPU, I think you will get that 100% CPU in any VM that you use that needs CPU processing.
Like danm66, that server is not supported.
This is the same as Dell SC1425 or 1950. It works for some models, but all the VMs have many times with the CPU between 80/100% use.
Jail
With this server and this CPU, I think you will get that 100% CPU in any VM that you use that needs CPU processing.
Like danm66, that server is not supported.
This is the same as Dell SC1425 or 1950. It works for some models, but all the VMs have many times with the CPU between 80/100% use.
Jail
ASKER
I ran this VM and this SQL db causing the CPU utlization for months and no problem. This just recently started a few days ago... I refreshed the install of the app (the app is on a physical server and saves to the SQL db on the VM) and ever since then I've noticed this. When using the SQL profiler I'm able to see which aspect of the db is causing the high CPU utilization, however, it's never done this before.
I seriously don't think it's an issue with my procs and/or compatibility for it's never done this in the past.
I seriously don't think it's an issue with my procs and/or compatibility for it's never done this in the past.
ASKER
Also,
I have 2 x DL 380 G4's running 7+ VM's and none of the other VM's do this.. And two of them are running the same version of SQL... I really think it's a software/db issues.. I have the stored procedures that it's choking on. I might end up contacting the software vendor...
I have 2 x DL 380 G4's running 7+ VM's and none of the other VM's do this.. And two of them are running the same version of SQL... I really think it's a software/db issues.. I have the stored procedures that it's choking on. I might end up contacting the software vendor...
I agree, contacting the s/w vendor sounds like a good next step. Sounds like there's something out of sync causing the procedure to get hung up.
ASKER
I'll call them and then will update the ticket. I used the SQL Profiler to determine what exact aspect of the DB is causing the issue. That should speed things up...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
How many vcpu's do you have assigned to the vm in question and how much RAM?
gopher_49 how were you able to see that in the profiler?