December 2, 2010 at 11:50 am
I am seeing the following message in SQL error logs which caused sql server to restart.
Sourcespid12s
Message
Service Broker manager has shut down.
How can i stop the broker service, if so what would be the drawbacks by stopping it, becasue we can nto really afford if SQL server is aut starting by itself.
Thanks
December 2, 2010 at 12:01 pm
Whoa, who's turning it off?
Implications: You've got an existing database(s) using service broker. These are feeding queues. Either the data on this server is going to become out of date because it stops picking up necessary data, or it's going to bloat because it stops sending it (which will also happen on the foreign source).
You need to find out why it's going down, or be incredibly sure it's not in use.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
December 2, 2010 at 12:17 pm
we don not use any features of service broker, all of our databases on that server are used only read purpose and there is no in flow or out flow of data from the server.
how can i stop it ? and how could find the reason as to who stopped it or why it gets stopped ?
December 2, 2010 at 12:34 pm
I also see this message in the error logs after 1 sec of the above message
SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
December 2, 2010 at 12:34 pm
Okay. Before I lead you down the wrong road, Service Broker stopping with that message can also happen due to a number of other causes, from MSDTC going wonky to other things, including a clustered node failover.
Are there other errors preceding this one in the log in a reasonable time frame, say, in the 15 minutes leading up to this?
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
December 2, 2010 at 12:36 pm
Tara-1044200 (12/2/2010)
I also see this message in the error logs after 1 sec of the above messageSQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
We cross posted. This is a user level stop request it received, I believe, unless another error triggered an automatic one. Service Broker didn't cause this, it was a victim of the preceding events.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
December 2, 2010 at 1:01 pm
so can i assume for SURE that someone else who has access has stopped it, if so how can i prove that?
fyi..4 people has admin access on this box.
December 2, 2010 at 1:45 pm
Tara-1044200 (12/2/2010)
so can i assume for SURE that someone else who has access has stopped it, if so how can i prove that?fyi..4 people has admin access on this box.
Without auditing already on the box? I'd check the server's application and system logs.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply