Google "SQL Server Static Ports" or any variation of it and you'll get a hundreads of thousands or more pages full of links and everyone will provind emost of what you need.

If you query is instead "How to Determine WHAT Port Number TO use" then forget about it, you get nothing.

I've found more articles then I can count on how to change SQL Server from dynamic port to fixed ports but not one on how to determine what port number to assign. I know there are lists of port numbers used by certain apps and services but that still doesn;t help me to deterine what poirt numbers I can or even should use for SQL Server. Do I just randomly piece together a set of 6 dgits or do I need to select from a specifi range and if yes what range and how do I detemrine if a port number is OK to use?

Perhaps this ia dumb question that everyone knows but me and thats why theres no hits for this query?

We're setting up Syetm Center 2012 and we have no choice but to go with Static ports. Does anyone have any suggestions on how I go about dertermining what post number(s) I can use/try?

The best I can provide is based on when I was setting up database mirroring. First, iirc, you need to select a port number above 1024, and I thought under 32768. When selecting this port number, work with your network services personnel to help identify an open port or range of open ports you can use such that they can document the port number(s) such that future applicatioins don't suddenly take the port(s) you and Network Services assigned.

Lynn Pettis (4/15/2013)The best I can provide is based on when I was setting up database mirroring. First, iirc, you need to select a port number above 1024, and I thought under 32768. When selecting this port number, work with your network services personnel to help identify an open port or range of open ports you can use such that they can document the port number(s) such that future applicatioins don't suddenly take the port(s) you and Network Services assigned.

Lynn,

It sound like the answer is (at least for me) ask your network admin for one or more ports you can use. That would explain why theres no SQL Server spefici hitys on what port number to use but still, it sure would be nioce it at least the Microsoft hosted items said something along the lines of..

"Unsure of what port number to use when assigning a fixed port to SQL Server? Check with your network admin for a range of valid port numbers to use with the SQL Server instances in your domain". Anything that would let the readr know that POrt Number selection is something that typically is handled by someone else.

just a suggestion, but in the past i've used port 14330 (1433 x 10)and also on my current dev machine, that has every version as an instance, they use ports 12005 for SQL 2005, 12008 for SQL 2008 (my R2 is the defailt instance) and 12012 for my SQL 2012.

just saying, it made sense at the time.

Lowell--There is no spoon, and there's no default ORDER BY in sql server either.Actually, Common Sense is so rare, it should be considered a Superpower. --my son

You'll find the HOSTS file here and also one titled SERVICES. Open the SERVICES file and it contains details of ports already assigned to services on the sever. Pick a port value not in use to ensure you have no service clashes.