\n
Related Documentation | \nVersion of up.time affected | \nAffected Platforms | \n
Verifying the Configuration of SQL Server Ports \n\t SQL Server Locks |
\n All | \nAll | \n
Overview
\n \nYou can configure an instance of SQL Server to use either static or dynamic ports.
\n \nConfiguring a Static Port
\n \nTo configure an instance of SQL Server to use a static port:
\n \nThe SQL Server Network Utility dialog box appears.
\nNote: If the TCP/IP protocol is disabled, enable it by clicking TCP/IP in the Disabled Protocols list box, and then clicking Enable.
\n
If TCP/IP protocol is disabled, enable it by clicking TCP/IP in the Disabled Protocols list box, and then clicking Enable.
\nThe static port that you specify must not be the same as the dynamic port on which your instance of SQL Server is currently listening. For example, if your instance of SQL Server is currently listening on dynamic TCP/IP port 1400, type 1500 for the new static port.
\nNote: The static port that you specify must not be the same as the dynamic port on which your instance of SQL Server is currently listening. For example, if your instance of SQL Server is currently listening on dynamic TCP/IP port 1400, type 1500 for the new static port.
\nTo configure your instance of SQL Server to use a dynamic port:
\nNote: If the TCP/IP protocol is disabled, enable it by clicking TCP/IP in the Disabled Protocols list box, and then clicking Enable.
\nIf TCP/IP protocol is disabled, enable it by clicking TCP/IP in the Disabled Protocols list box, and then clicking Enable.
\nIf you have a clustered instance of SQL Server, and you follow the specified steps on a cluster node, you may notice that the TCPDynamicPorts and TCPPort registry values on other cluster nodes retain the old values. When you move the SQL Server group to the corresponding cluster node, and then bring SQL Server online on the cluster node, the registry values on the cluster nodes will reflect the updated values.
\n