Post reply

Determining if SQL Browser stopped running within a certain time frame

  • January 9, 2017 at 12:09 pm

    #333384

    Hi,

    Is there a way to check if the SQL Browser stopped running at a particular time during the day?

    I was just curious if there was some kind of log file that would keep track of this kind of information.

    Thanks!

  • January 9, 2017 at 1:34 pm

    #1921487

    The only way I know of is to access WMI programmatically and periodically to check the status of the service.

  • January 9, 2017 at 1:40 pm

    #1921489

    Ok, thank you for replying. I may look into your suggestion. There is a sporadic communication problem I'm running into where an OLAP server cannot establish a connection to an OLTP server which results in this error being generated: "SQL Server does not exist or access denied".

    I understand the SQL Browser is used to figure out the IP address for a given server name (although I'm not certain if this is true or not) so I was thinking that the connection problem I'm having is due to the SQL Browser failing to run at times on the OLAP server.

    Thanks again

  • January 9, 2017 at 1:51 pm

    #1921493

    The SQL Browser service does not resolve IP addresses...DNS does that. It provides information about the instances on a server and the port numbers used for each instance. See the following: https://technet.microsoft.com/en-us/library/ms181087(v=sql.105).aspx

    Here's a few things to look at if the SSAS instance isn't connecting:

    * It could be a DNS issue. Try to use the IP address and port of the source OLTP server in the connection string.

    * The connection may be timing out. Set the connection timeout properties in SSAS to see it that helps.

  • January 9, 2017 at 2:00 pm

    #1921496

    Thanks for the information. I will make a note of it.

    "It could be a DNS issue. Try to use the IP address and port of the source OLTP server in the connection string."

    Yes, I had emailed one of the dbas earlier today and suggested they modify the OLAP data sources to reference the IP addresses. Currently, it just has the server name and port. Hopefully, this will fix the problem. I had thought this was done already, but I had only did it in the connection managers in the SSIS packages which are run from a job server.

    "Set the connection timeout properties in SSAS to see it that helps. "

    Ok, I will look into this and possibly pass it on to our dbas.

    Thanks again for your help.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply