patternsqlMinor
Port number change
Viewed 0 times
numberchangeport
Problem
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?
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?
Solution
- 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.
Context
StackExchange Database Administrators Q#1813, answer score: 5
Revisions (0)
No revisions yet.