Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

The Voice of the DBA

Steve Jones is the editor of SQLServerCentral.com and visits a wide variety of data related topics in his daily editorial. Steve has spent years working as a DBA and general purpose Windows administrator, primarily working with SQL Server since it was ported from Sybase in 1990. You can follow Steve on Twitter at twitter.com/way0utwest

Finding SQL Server Client Ports

I saw a post recently asking if there was an easy way to find the port a client was using on a SQL Server since someone had multiple instances. I asked for some information since there are actually multiple ports in use.

The port the SQL Server listens on

The port the client server opens a connection on their side

The first one comes from a few places. It’s easily found in the Configuration Manager GUI as shown below:

SQLServerPort

These are the TCPIP properties for my service.

Finding the client port, which is probably needed for tracing/troubleshooting, is easy to do as well. You can query sys.dm_exec_connections, and see how clients are connected. I don’t have any TCP connections on my instances, since I am local it’s through shared memory, but here’s where you’d find it in the result set:

SQLServerPort2 

I’ve typically not worried about port, but the client_net_address has been valuable to me in the past.

Comments

Posted by Jason Brimhall on 17 June 2010

That is a highly useful DMV.  Thanks Steve.

Posted by Steve Jones on 17 June 2010

I thought it was pretty cool. I was sure that it was stored somewhere since I've had similar needs in the past.

Leave a Comment

Please register or log in to leave a comment.