|
Home > Archive > MS SQL Server > October 2006 > SQL Server pegs one core constantly
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SQL Server pegs one core constantly
|
|
| ian.beyer@gmail.com 2006-10-24, 6:29 pm |
| I recently got SQL Server 2005 Standard (x64) operating on our new
PowerEdge 2950 (4 Xeon cores), and the SQL server process almost
constantly pegs one of the 8 threads and sucks up about 1.2-2 GB of
memory, and we haven't even started hitting it hard - The only
databases currently on that server are the backend for McAfee
ProtectionPilot (ePO) and the database for our ticketing system (20-30
tickets a day, shouldn't even be breaking a sweat)...
So why is it chewing up so much CPU? Process Explorer isn't sowing any
child threads, jsut the sqlserver.exe as a child of services.exe
| |
| Andrew J. Kelly 2006-10-24, 6:29 pm |
| Run a profiler trace to see what is eating up all the CPU.
--
Andrew J. Kelly SQL MVP
<ian.beyer@gmail.com> wrote in message
news:1158616345.157208.194410@i3g2000cwc.googlegroups.com...
>I recently got SQL Server 2005 Standard (x64) operating on our new
> PowerEdge 2950 (4 Xeon cores), and the SQL server process almost
> constantly pegs one of the 8 threads and sucks up about 1.2-2 GB of
> memory, and we haven't even started hitting it hard - The only
> databases currently on that server are the backend for McAfee
> ProtectionPilot (ePO) and the database for our ticketing system (20-30
> tickets a day, shouldn't even be breaking a sweat)...
>
> So why is it chewing up so much CPU? Process Explorer isn't sowing any
> child threads, jsut the sqlserver.exe as a child of services.exe
>
|
|
|
|
|