Using the tcp: prefix for SQL Server connections : Force use of TCP protocol

05 September,2014 by Jack Vamvas

Question: I’ve been advised to use the prefix tcp:   for a SQL Server connection, during some connection troubleshooting.  Could you explain the purpose of using the tcp: prefix , such as :

Tcp:MYSERVER\INSTANCE1

Answer: The tcp:  prefix will force the usage of TCP/IP transport.  There are certain situations , where using the tcp: will allow a valid  SQL Server connection.

When using the tcp: prefix you’re requesting to explicitly connect through TCP/IP. If the server is not listening on TCP/IP , your options are either to not use the tcp: prefix or  locate and enable the tcp protocol. Use the SQL Server Configuration Manager | SQL Server Network Configuration tab for the SQL Server Instance.

Tcp_protocol

Read More

Cannot connect to SQL Server

SQL Server - Login failed for user 'username'. The user is not associated with a trusted SQL Server connection

SQL Server Versions


Author: Jack Vamvas (http://www.sqlserver-dba.com)


Share:

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment on Using the tcp: prefix for SQL Server connections : Force use of TCP protocol


sqlserver-dba.com | SQL Server Performance Tuning | SQL Server DBA:Everything | FAQ | Contact|Copyright & Disclaimer