SQLServerCentral / Discuss Content Posted by Steve Jones / Article Discussions / Article Discussions by Author / SQL Server Browser / Latest Posts

RE: SQL Server Browser

Arun Jebakumar — Thu, 21 Jul 2011 13:44:39 GMT

By default, SQL Browser is installed with the Express editions, and since thats always a named instance this is always being required!! There are many non-DBAs who could accidentally disable this service and face trouble in connecting to their instances..by the way, it appears that we can disable the browser service and instead always use the server name along with the port number for connecting to the SQL instance (from within the application).

RE: SQL Server Browser

Mohit K. Gupta — Tue, 25 Nov 2008 09:55:42 GMT

[quote][b]Steve Jones - Editor (11/25/2008)[/b][hr]Perhaps things are mis-worded, but I think the answer is fine.Connecting via IP and port would be connecting to my local server as 127.0.0.1, 1433That would not use the Browser service. If I connected via SJONES, then the Browser would return the IP and port to my client, which would then connect.[/quote]I just read it again, I agree. Its one of those Microsoft certification questions, its sounds like but not quite what the question was asking heh. I guess if the option was "provide ip/port information", then it would be a correct option.

RE: SQL Server Browser

A_A_R_T — Tue, 25 Nov 2008 09:51:50 GMT

Clear. Thanks for your explanation. I'm always having difficulties with semantics :unsure:

RE: SQL Server Browser

Cliff Jones — Tue, 25 Nov 2008 09:24:00 GMT

OK, I understand what you are saying. If my client connects by specifying the IP and Port then it would not use or need the Browser Service. Thanks for the explanation.

RE: SQL Server Browser

Steve Jones - SSC Editor — Tue, 25 Nov 2008 09:01:26 GMT

Perhaps things are mis-worded, but I think the answer is fine.Connecting via IP and port would be connecting to my local server as 127.0.0.1, 1433That would not use the Browser service. If I connected via SJONES, then the Browser would return the IP and port to my client, which would then connect.

RE: SQL Server Browser

Mohit K. Gupta — Tue, 25 Nov 2008 07:54:21 GMT

Aaa I am late :(. But I agree with it, I was talking to Microsoft Engineer on recent course. Because every book tells me to turn of Browser service as it is not required. So I ask him why the heck Microsoft made it if most people recommend it to disable it. After talking, it turned out the Browser service is required if you use a non-standard port for SQL Server. If you a non-standard port, and you have the browser service turned off, then you did have to enter the port information into the connection properties.:).

RE: SQL Server Browser

A_A_R_T — Tue, 25 Nov 2008 07:47:09 GMT

I'll be the fourth then :P

RE: SQL Server Browser

Joe Burdette — Tue, 25 Nov 2008 07:38:45 GMT

Agreed, I third the motion… ;)

RE: SQL Server Browser

Cliff Jones — Tue, 25 Nov 2008 07:31:12 GMT

I was just about to make the same point. It seems that Conecting via TCP/IP should be correct also?

RE: SQL Server Browser

ghollis — Tue, 25 Nov 2008 07:28:57 GMT

The link provided in the answer states, "When SQL Server clients request SQL Server resources, the client network library sends a UDP message to the server using port 1434. SQL Server Browser responds with the TCP/IP port or named pipe of the requested instance. The network library on the client application then completes the connection by sending a request to the server using the port or named pipe of the desired instance."Does this not contradict the reported explanation?

SQL Server Browser

Steve Jones - SSC Editor — Mon, 24 Nov 2008 23:51:30 GMT

Comments posted to this topic are about the item [B]SQL Server Browser[/B]