Can two clustered SQL instances on a 2003 windows cluster use the same 1433 tcp port setting reliably?

It seems to be up and working right now.

link|improve this question

80% accept rate
feedback

2 Answers

up vote 1 down vote accepted

Microsoft says no. The named instance should technically not be listening on port 1433. If both instances are set to listen on the static port 1433 and it's working then maybe something in the cluster environment is allowing it. I'd be a little skeptical of it myself.

link|improve this answer
I've found a few other sources advising against it as well. Each virtual sql server name has it's own IP so it seems it would be OK there. My concern is what happens between the virtual sql server and the physical server - how that data is actually moved. – Sam Apr 13 '10 at 22:27
feedback

We've actually had 3 instances running SQL 2005 in a Windows 2003 cluster for about 3 years using the default port settings and have had no issues at all. When running normally, we are running 2 instances on one node and 1 instance on the other and the failover has worked flawlessly as well.

link|improve this answer
1  
Have you actually changed all the ports to 1433? The default port setting for named instances is to listen on dynamic ports. – Sean Howat Apr 13 '10 at 17:14
They are all set to 1433, none were manually configured to this port. – jjrab Apr 22 '10 at 16:14
feedback

Your Answer

 
or
required, but never shown

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