January 10, 2014 at 9:57 am
Hi all
I think I know the answer to this question, however, I'd like to run it by you guys, if that's ok..
I have an SQL 2008 server, with 5 instances. I've been having an ongoing issue with the SQL browser and it's getting worse all the time, where the SQL Browser just stops accepting connections. I can open up SMSS on the server itself and I can connect to all instances, but from anything external, no dice. I restart the SQL Browser, everything works fine. Biggest problem is there are no tell tale signs that'll allow me to capture the problem before a user does, I wanted to setup something in orchestrator that would auto restart the browser, but there's literally nothing, no event log in windows or SQL, no errors, nada.
All instances are currently SP1, I've looked at details of SP2 and it looks like there's a bug fix in the Service Pack that will fix this horribly annoying problem. Question is, as this is a shared resource, I presume that I can service pack just one of the instances and as the SQL Browser is a shared component, and that will up the SQL Browser (and all SQL binaries) to the latest service pack, thus resolving my problem.
Can someone confirm if this is correct and also if there are any side affects to only applying the Service Pack to on instance?
Thanks for taking the time to read and offer advice in advance
Mark C
January 13, 2014 at 2:28 am
*bump* anyone help?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply