Post reply

SQL Server Browser

  • January 15, 2014 at 8:59 pm

    #288420

    Comments posted to this topic are about the item SQL Server Browser

  • January 15, 2014 at 8:59 pm

    #1680494

    Had to do some digging for this one - nice question thanks.

    Hope this helps...

    Ford Fairlane
    Rock and Roll Detective

  • January 15, 2014 at 10:51 pm

    #1680513

    Good One!

    ---------------------------------------------------
    "Thare are only 10 types of people in the world:
    Those who understand binary, and those who don't."

  • January 16, 2014 at 1:07 am

    This was removed by the editor as SPAM

  • January 16, 2014 at 1:07 am

    #1680539

    Nice question, but a bit ambiguous.

    I can start SQL Server Browser with the command net start sqlbrowser.

    No switches there 😉

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • January 16, 2014 at 1:57 am

    #1680557

    Koen Verbeeck (1/16/2014)

    Nice question, but a bit ambiguous.

    I can start SQL Server Browser with the command net start sqlbrowser.

    No switches there 😉

    I agree it's a nice question but ambiguous.

    The question is more about which switch allows you to run the service in a command prompt window rather than starting the service from the command prompt.

    Running sqlbrowser.exe -c does not start the SQLBrowser service. Run the command then check your local services. The switch runs the service in the command prompt window and displays logging info for troubleshooting. You will notice the first line is

    SQLBrowser: starting up in console mode

    The SQL Guy @ blogspot[/url]

    @SeanPearceSQL

    About Me[/url]

  • January 16, 2014 at 5:37 am

    #1680610

    Another thumbs down on QOTD.

    Use ' net start sqlbrowser '

  • January 16, 2014 at 6:41 am

    #1680621

    Yes, the question is a little ambiguous, but that has no impact on the answer, since the service itself is not listed as an option (with no switches).

    Definitively not a "thumbs down" question.

    Best Regards,

    Chris Büttner

  • January 16, 2014 at 6:57 am

    #1680632

    So easy I thought it was Monday. Thanks!

    And, yes, it was a bit ambiguous. But, unlike the question I cried foul on earlier this week, you didn't have to mind read to get the correct answer. Can I give it a "thumbs sideways"?

    [font="Verdana"]Please don't go. The drones need you. They look up to you.[/font]
    Connect to me on LinkedIn

  • January 16, 2014 at 9:01 am

    #1680708

    Just don't give it the finger 🙂

    I did not mind the question at all. Thank you for the contribution.

  • January 20, 2014 at 7:59 am

    #1681560

    net start SQLBrowser will not show you the client IP/ports from which they try to connect or how many times they try before disconnecting, like this:

    CLNT_UCAST_INST w/refresh from 10.94.49.224[61784]

    CLNT_UCAST_INST from 10.94.49.224[61784]

    [7256]: Waiting for next request...

    [7248]: Received request...

    [7248]: Waiting for next request...

    [7092]: Received request...

    CLNT_UCAST_INST w/refresh from ::1[61785]

    CLNT_UCAST_INST from ::1[61785]

    [7092]: Waiting for next request...

    [7248]: Received request...

    [7248]: Waiting for next request...

    [7248]: Received request...

    CLNT_UCAST_INST w/refresh from 10.94.49.224[61786]

    CLNT_UCAST_INST from 10.94.49.224[61786]

    [7248]: Waiting for next request...

    [7256]: Received request...

    CLNT_UCAST_INST w/refresh from ::1[61787]

    CLNT_UCAST_INST from ::1[61787]

    [7256]: Waiting for next request...

    [7092]: Received request...

    [7248]: Received request...

    [7248]: Waiting for next request...

    [7092]: Waiting for next request...

    [7248]: Received request...

    CLNT_UCAST_INST w/refresh from 10.94.49.224[61788]

    CLNT_UCAST_INST from 10.94.49.224[61788]

    [7248]: Waiting for next request...

    [7092]: Received request...

    CLNT_UCAST_INST w/refresh from ::1[61789]

    CLNT_UCAST_INST from ::1[61789]

    [7092]: Waiting for next request...

    [7256]: Received request...

    [7248]: Received request...

    [7248]: Waiting for next request...

    [7256]: Waiting for next request...

    [7092]: Received request...

    CLNT_UCAST_INST w/refresh from 10.94.49.224[61790]

    CLNT_UCAST_INST from 10.94.49.224[61790]

    [7092]: Waiting for next request...

    [7248]: Received request...

    CLNT_UCAST_INST w/refresh from ::1[61791]

    CLNT_UCAST_INST from ::1[61791]

    [7248]: Waiting for next request...

    [7256]: Received request...

    [7256]: Waiting for next request...

    [7092]: Received request...

    [7092]: Waiting for next request...

  • January 20, 2014 at 3:53 pm

    #1681691

    Koen Verbeeck (1/16/2014)

    Nice question, but a bit ambiguous.

    I can start SQL Server Browser with the command net start sqlbrowser.

    No switches there 😉

    I didn't know it could be started from command line without using net start until I saw this question. But a google search for SQL server Browser command line switches led me to http://technet.microsoft.com/en-us/library/ms181087%28v=sql.105%29.aspx (Google found that rather than the page referenced in the explanation, and Bing found absolutely nothing useful) so it was easy to get the answer.

    Tom

  • January 21, 2014 at 9:21 am

    #1682040

    interesting question..

    Thanks.

Viewing 13 posts - 1 through 12 (of 12 total)

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