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

SQLTechnet

Vinoth is currently a Senior SQL Server DBA and 10 years of experience as SQL Server DBA. Started my career as a DBA in SQL 6.5/7 has worked in all subsequent SQL Server version. Vinoth has worked in some of the largest SQL server environments in the world in various domains ranging from Finance, Retail, Manufacturing, Consulting, Web etc. Vinoth has Engineering Degree in Computer Science and has certified in MCITP - Database Adminstrator in 2008/2005, MCDBA and ITIL Foundation V3.

Forcing network protocol to connect SQL server


Whenever there is a network issue or a SQL server browser issue we might need to connect SQL server in different network protocols to troubleshoot. We can change the default protocol in configuration manager but it will make the change globally for all connection connecting to the SQL instance, instead we can force the protocol for your connection alone pretty easily by appending the protocol name to the servername in SSMS, SQLCMD or any source connecting to the SQL instance like

Forcing TCP:

  

Forcing Named Pipes:-



Similarly we can force protocol while connecting through SQLCMD or through any source.

Comments

Leave a comment on the original post [www.sqltechnet.com, opens in a new window]

Loading comments...