RE: How to change from Dynamic Ports to Static Ports on SQL Cluste

Tech-Archive recommends: Fix windows errors by optimizing your registry

Linchi thanks for your reply. We haven't actually tried to make the change
yet. We are looking for guidence on making this change, since it is on a SQL
cluster, built on top of a Windows cluster and these kinds of changes can
become complex. We have another question also. When we change this port is it
recommended to use the default port 1433 or another port?


"Linchi Shea" wrote:

Did you try Configuration Manager? If the SQL instance is under the cluster
control, there is no quorum checkpoint changing it back. Rather, the
cluster/quorum checkpoint will replicate the change to the other node. Did
you run into any issue?

Linchi

"Ken" wrote:

I am not sure if this should be posted in SQL Server 2008 Setup or here:

We are planning to move a middle tier machine into our DMZ. Our clients will
be connecting to the middle tier machine with a .NET application using web
services. The web services on the middle tier machine currently connect to
our SQL Server 2008 environment to move data between the SQL Server and the
Client Application. We currently have a 2 node SQL 2008 Active/Active Cluster
running
on 2 node Windows 2003 Cluster. When set up the default installation created
the settings for the IPAll as displayed below for SQL1 and SQL2. We need to
change these settings from TCP Dynamic Ports to TCP Port 1433 on both servers
for security purposes. What are the best practices for making this change in
the environment above? Is there any istructions anywhere from Microsoft to
make this
change on an existing cluster? How do we make the change without the
checkpointing to the quorum changing the Ports back? Do we need to take the
SQL Service offiline? What are the recommended steps?

SQL1:
IPAll
TCP Dynamic Ports 1304
TCP Port


SQL2:
IPAll
TCP Dynamic Ports 1717
TCP Port
.

Relevant Pages

  • Re: client cant connect when instance on one particular node
    ... Best practice is to specify a specific port and then code the client to ... SQL 2000 SP4 for SQL version. ... Then server guys evicted ... cluster configuration. ...
    (microsoft.public.sqlserver.clustering)
  • RE: How to change from Dynamic Ports to Static Ports on SQL Cluster?
    ... If the SQL instance is under the cluster ... cluster/quorum checkpoint will replicate the change to the other node. ... We currently have a 2 node SQL 2008 Active/Active Cluster ... change these settings from TCP Dynamic Ports to TCP Port 1433 on both servers ...
    (microsoft.public.sqlserver.clustering)
  • Re: Problem communicating to SQL default instance with OLE DB Prov
    ... DBNETLIB is old and doesn't understand the subtleties of SQL Server 2005. ... instance static port to 1434. ... Try changing the default instance back to TCP port 1433. ...
    (microsoft.public.sqlserver.connect)
  • Re: Change dynamic port to standard 1433 per named instance
    ... Since each instance has its own IP address, you can use the same port number on multiple clustered instances. ... I have had some strangenesses with older versions (SQL 2000) and using 1433 for a named instance so be sure and test first. ... the standard 1433 port in a cluster environment. ...
    (microsoft.public.sqlserver.clustering)
  • RE: How to change from Dynamic Ports to Static Ports on SQL Cluste
    ... Different places have different guidelines for picking a port. ... We are looking for guidence on making this change, since it is on a SQL ... cluster, built on top of a Windows cluster and these kinds of changes can ... change these settings from TCP Dynamic Ports to TCP Port 1433 on both servers ...
    (microsoft.public.sqlserver.clustering)