Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We're trying to diagnose the cause of slowness on our Database server.

We're running the latest rev SQL Server 2005 on Windows 2008x64.

The behavior that we're seeing is this: We see the SYSTEM process spike one of the CPUs for about 2 minutes, during this time SQL server slows down by a factor of 10. The slowness lasts until SYSTEM is done, then in an hour everything starts again.

During these slowdowns disk writes don't spike, paging doesn't spike, the only noticeable precursor we see is that SYSTEM maxes out one of the sixteen (HT)CPUs.

Note that this doesn't happen at the top of the hour, it just happens once an hour, and it shifts a bit depending on the length of the incident.

At the moment this is causing intermittent slowdowns, but when the server is really busy it can cause Worker Thread starvation.

The server is a Dual Quad Dell R710 with 96GB of RAM and RAID10 data/log disks.

Has anyone experienced this kind of problem? Does anyone know where we should look?

Edit: SQL Server Version is 9.0.4035

share|improve this question
    
Please post your build number for SQL 2008. Anything else installed on the server? –  TomTom Mar 22 '10 at 18:08

1 Answer 1

up vote 2 down vote accepted

We did quite a bit of experimentation on this:

  • We tried stopping Hyperic.
  • We tried freeing up one CPU for the OS to have.
  • We locked SQL server in memory and made sure to reserve 10GB for the OS.
  • We added and rebuilt lots of indexes.

Finally: We eliminated the periodic slowness by stopping the four DSM tasks associated with Dell OpenManage Server Administrator (OMSA).

Doing this immediately ended the periodic slowness issues and resulted in more consistent performance throughout the hour.

share|improve this answer
    
I've also seen a bad printer driver and the print spooler service on a SQL Server do this. If you are running a Print Spooler service on a SQL Server and don't need it running, then stop it and set it to Manual. –  ServerChecker Jun 11 '10 at 5:11

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.