|
|
Posted by Erland Sommarskog on 11/23/05 15:40
> This problem occurs everytime. I have just reproduced it again and the
> results of sp_who2 are below:
>...
>
> Sorry about the formatting. As you can see the only runnable process is
> the sp_who2 command. And the user for the application is not in the
> list of Logins so it cannot be anything related to the application.
Hm, there is a lot of CPU on the Lazy Writer given the login time.
Could that be a token of something? (I'm just thinking aloud.)
> I do have this message in the error log though from when I started up
> the instance this morning:
>
> 2005-11-23 10:48:54.00 spid51 Starting up database 'msdb'.
> 2005-11-23 10:49:11.92 spid51 Error: 15457, Severity: 0, State: 1
15457 is change of configuration option.
> Incidentally, this does occur on another 2 machines I have tried it on
> and so I do not think it is a hardware problem.
Interesting indeed.
> Maybe I should try and raise this with Microsoft unless you can think
> of anything else?
I would definitely open a case for this. This smells very fishy to me.
If this indeed is a bug in SQL Server, you should be refunded anything
you are charged initially. Of course, if there is indeed something bad
in your environment, you will have to pay.
OK, one idiot check before you call: you are not using compressed drives
are you?
--
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
Navigation:
[Reply to this message]
|