Posted by Erland Sommarskog on 12/09/05 20:59

Ian Murphy (ian@integra-xp.com) writes:
> Hi, I've just picked up on this thread. I am also having the same
> problem. Configuration is a 2003svr with sql server with sp4.
>
> I am seeing exactly the same symptoms and have tried the suggestions
> posted in this thread, all no no avail.
>
> We're a small consultancy and have a collection of db's for various
> packages mounted on the server. The server behaved normally until a few
> days ago. I don't know what changed but I initially attacked disk and db
> fragmentation and rebuilt the indexes to see if that was the cause - no
> luck.
>
> The cpu simply sits at 100% for the sqlserver process.
>
> If anyone wants to make any suggestions this is not a production server
> so I'm open to ideas.
>
> What does work is taking the db's offline and putting them online again
> - not exactly an ideal solution.
>
> Unfortunatly the problem only rears its head occasionally and once you
> have taken 7 o 8 db's offline it goes away. I am not sure the problem is
> being caused by the last one to be taken offline.

Well, in the case of Paul's databases, it happened with his in-house
servers, but not at the customer site with the same database. That was
sort of strange. Also, in Paul's case, he had exactly what operation
that caused the condition. It does not seem that you have not identified
anything similar, but it your case it just happens. Out of the blue,
I would guess on autogrow.

All that I can really suggest at this point is to identify exactly
which database you need to take off-line for the situation to resolve.
Of course setting up a Profiler trace with selected events may be an
idea.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]