Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are planning on setting a static port for SQL Server 2005/2008 failover clustering. Any guide on what port to choose/select for 4 nodes of each cluster?(Active/Active) I am also thinking some applications need to know about the static port. What is the best way of knowing which application is setup to use default port from the SQL instance? In general, what is the best way of implementing port number change on sql server failover clustering?

share|improve this question
up vote 3 down vote accepted

The port number you select doesn't matter. Static port numbers should only be needed if you need to specify holes through a firewall which isn't on the local server. All SQL Server client drivers can convert the instance name to the TCP port number automatically using the SQL Server Browser.

The nice thing about using dynamic port numbers is that the TCP port will always be available. If you specify a static port number, there is a risk that something else will grab that port before SQL Starts up (I've seen this happen before) which will cause SQL to start without grabbing the port.

share|improve this answer
Thank you for taking the time to respond to my question. I also came across this… And, my question is do you recommend changing the default port and the dynamic port to static ports? – db7 Mar 27 '11 at 23:09
I always recomend against changing the port number. It does nothing for you but make more headache. – mrdenny Mar 28 '11 at 19:20
Thank you very much, Sir! – db7 Mar 29 '11 at 2:19
  • Sequential port numbers for each instance. Just pick some.
  • Port numbers that match instance name (eg xxx1 = InstanceA, xxx2 = InstanceB)
  • No app this century should require "default" port 1433. They should resolve instance name. Only the default instance (which won't apply here) should use 1433.
  • If you change the port, some clients may cache the value but it should just work. If this is a new cluster then you shouldn't need to change anything.
share|improve this answer

I remember when working with clusters that the port change from dynamic to a static one doesn't take effect if you don't disable the checkpointing of the quorum.

Here are more details: How to Change the Dynamic Port of the SQL Server Named Instance to an Static Port in a SQL Server 2005 Cluster

Also, applications managers should be notified about the port change because there are places where this can be used. As well, the port of SQL Server Instance is used in Firewall settings in many types of network configurations.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.