August 7, 2012 at 3:38 pm
If I am using dynamic port settings on my sql server instance, I need the sql browser service to run and listen over port 1434 for incoming requests.
If I am using a static default port of 1433, the browser service is not needed.
However, if I set a non-default port, say 1638, for my SQL server to listen over, do I need the SQL Browser to listen for incoming requests, so it can look up 1638???
My understanding is, as a connection coming into a sql server instance, if it is not using dynamic ports, and not using the default port, I MUST KNOW the port SQL Server is listening on and use that port in my connection string to make a succesfful connection.
I always thought the browser service was only needed for dynamic ports.
August 7, 2012 at 9:10 pm
"However, if I set a non-default port, say 1638, for my SQL server to listen over, do I need the SQL Browser to listen for incoming requests, so it can look up 1638???"
-- Browser service means to direct client request to dynamic ports. If you intend to use 1638 (static port), use it in connection string. So that browser service will be bypassed.
My understanding is, as a connection coming into a sql server instance, if it is not using dynamic ports, and not using the default port, I MUST KNOW the port SQL Server is listening on and use that port in my connection string to make a succesfful connection.
-- Yes
I always thought the browser service was only needed for dynamic ports.
-- yes, its not needed for a static port.
August 7, 2012 at 9:15 pm
Keep in mind that should you ever need to use the dedicated admin connection, the browser service will need to be running and 1434 will need to be accessible.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 8, 2012 at 12:17 am
Firstly, are these questions related to firewall configuration for a SQL server instance?
alanspeckman (8/7/2012)
If I am using dynamic port settings on my sql server instance, I need the sql browser service to run and listen over port 1434 for incoming requests.
Yes and this is really the only way as the dynamic port could change each time the instance restarts
alanspeckman (8/7/2012)
If I am using a static default port of 1433, the browser service is not needed.
That is correct
alanspeckman (8/7/2012)
However, if I set a non-default port, say 1638, for my SQL server to listen over, do I need the SQL Browser to listen for incoming requests, so it can look up 1638???
If you'll be connecting directly to the IP,port then you don't need the browser service, it's only needed when connecting using the instance name
alanspeckman (8/7/2012)
My understanding is, as a connection coming into a sql server instance, if it is not using dynamic ports, and not using the default port, I MUST KNOW the port SQL Server is listening on and use that port in my connection string to make a succesfful connection.
See above
alanspeckman (8/7/2012)
I always thought the browser service was only needed for dynamic ports.
No, although it is only really more relevant when dynamic ports are used as they can change at any restart
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 8, 2012 at 8:12 am
SQLRNNR (8/7/2012)
Keep in mind that should you ever need to use the dedicated admin connection, the browser service will need to be running and 1434 will need to be accessible.
Didn't know that, thanks!
August 9, 2012 at 8:24 am
So,
Browser service needed:
1. If connecting using only the instance name with a non-standard port
2. If connecting to an instance that uses dynamic ports, such as a named instance because it is configured to use dynamic ports initially when installed.
Browser service not needed
1. If connected to an instance using standard port 1433?
2. If using the IP address and the port number of the sql server instance.
Is #1 in both categories above correct? If not, can you please correct me?
Thanks,
Alan.
August 9, 2012 at 11:28 am
alanspeckman (8/9/2012)
So,Browser service needed:
1. If connecting using only the instance name with a non-standard port
2. If connecting to an instance that uses dynamic ports, such as a named instance because it is configured to use dynamic ports initially when installed.
yes and yes
alanspeckman (8/9/2012)
Browser service not needed1. If connected to an instance using standard port 1433?
2. If using the IP address and the port number of the sql server instance.
Is #1 in both categories above correct? If not, can you please correct me?
Thanks,
Alan.
again, yes and yes
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 13, 2012 at 1:10 pm
Thank you all for reading and thank you Perry for your replies. 🙂 Great community here.
One last question.
Is it possible for 2 SQL Server instances running on the same server to share the same port? I have tested this and it isn't possible from what I have tested so far.
Is it possible?
August 13, 2012 at 2:57 pm
alanspeckman (8/13/2012)
Thank you all for reading and thank you Perry for your replies. 🙂 Great community here.One last question.
Is it possible for 2 SQL Server instances running on the same server to share the same port? I have tested this and it isn't possible from what I have tested so far.
Is it possible?
No, they would need a separate IP address stacked on the NIC or a totally separate NIC
For example if i have a server with a single NIC, i have 2 IP addresses stacked as
10.10.10.41 255.255.255.0
10.10.10.42 255.255.255.0
i could then set one instance to listen on
10.10.10.41, 1433
and another on
10.10.10.42, 1433
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 13, 2012 at 5:37 pm
At the risk of adding confusion you can connect to an instance using a nonstandard (not dynamic) port and the server name without the browser service.
example: Servername.domainname\instancename,port_number
August 14, 2012 at 6:38 am
andersg98 (8/13/2012)
At the risk of adding confusion you can connect to an instance using a nonstandard (not dynamic) port and the server name without the browser service.example: Servername.domainname\instancename,port_number
not confusing, makes sense, DNS would resolve the name to an IP.
Also, thank you for the multiple IP/port example. That makes alot of sense.
Alan.
August 14, 2012 at 6:54 am
andersg98 (8/13/2012)
At the risk of adding confusion you can connect to an instance using a nonstandard (not dynamic) port and the server name without the browser service.example: Servername.domainname\instancename,port_number
you specify the instance name or the port number not both
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 14, 2012 at 7:19 am
Perry Whittle (8/14/2012)
andersg98 (8/13/2012)
At the risk of adding confusion you can connect to an instance using a nonstandard (not dynamic) port and the server name without the browser service.example: Servername.domainname\instancename,port_number
you specify the instance name or the port number not both
Think it will still work, the instance name is just ignore
If you want to test i'd recommend using servername.domain\bacon,port_number I actually managed to convince one of our sysadmins we had a named instance called 'bacon' using this for SSMS
August 14, 2012 at 8:41 am
that's as maybe, but the idea is to specify port or instance name. Both just serves to cause some people confusion
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 14, 2012 at 9:16 am
Re:
Keep in mind that should you ever need to use the dedicated admin connection, the browser service will need to be running and 1434 will need to be accessible.
I have just set my browser service to stop and amended my tcp/IP all properies to use dynamic ports and re-started the SQL service and I can connect using DAC - SQL 2008R2 D/E, so I'm not sure that statement is true??
However, my instance is the default and I always thought you only need the browser service for named instances.
SQL DBA
Every day is a school day, and don't trust anyone who tells you any different.
http://sqlblogness.blogspot.co.uk
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply