December 25, 2008 at 2:32 am
The CPU of SQL server start growing to 100%.
I found that it happens because SQL is busy to write a lot of events :
The activated proc [UserName].[SqlQueryNotificationStoredProcedure-30f756a7-ca59-4561-8ef2-fa57ac60b7a9] running on queue DBName.UserName.SqlQueryNotificationService-30f756a7-ca59-4561-8ef2-fa57ac60b7a9 output the following: 'Text for 'SqlQueryNotificationStoredProcedure-30f756a7-ca59-4561-8ef2-fa57ac60b7a9' is missing from syscomments. The object must be dropped and re-created before it can be used.'
in SQL server ErrorLog.
Can anbody tell me , how this error raises in Log continuesly(many times in second firing continues) .Is there any services for that?
Or how can i stop it?
December 26, 2008 at 9:04 am
Run this:
select * from sys.service_queues
These are messages from service broker queue. It looks from message that you need to recreate the notification procedure in question.
MJ
December 26, 2008 at 9:19 am
Do you know what this proc was doing? Or what this was doing in Service Broker? There is likely a triggering event (message, proc, etc.) that is causing this as well.
December 28, 2008 at 10:24 pm
But i have already disable broker service on database , even though i am getting the thread of this serrvice in sysprocesses..
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply