Skip to content

creating-a-valid-connection-string-using-tcp-ip.md

Latest commit

 

History

History
170 lines (122 loc) · 6.83 KB

creating-a-valid-connection-string-using-tcp-ip.md

File metadata and controls

170 lines (122 loc) · 6.83 KB
title Creating a Valid Connection String Using TCP IP | Microsoft Docs
ms.custom
ms.date 06/13/2017
ms.prod sql-server-2014
ms.reviewer
ms.technology configuration
ms.topic conceptual
helpviewer_keywords
connection strings [Database Engine]
ports [SQL Server], connecting to
TCP/IP [SQL Server], connection strings
connection strings [Database Engine], TCP/IP
aliases [SQL Server], TCP/IP
ms.assetid ee5dbc2c-1fc6-42bd-bdf5-efa792557934
author stevestein
ms.author sstein
manager craigg

Creating a Valid Connection String Using TCP IP

To create a valid connection string using TCP/IP, you must:

  • Specify an Alias Name.

  • For the Server, enter either a server name to which you can connect using the PING utility, or an IP address to which you can connect using the PING utility. For a named instance append the instance name.

  • Specify TCP/IP for the Protocol.

  • Optionally, enter a port number for the Port No. The default is 1433, which is the port number of the default instance of the [!INCLUDEssDE] on a server. To connect to a named instance or a default instance that is not listening on port 1433, you must provide the port number, or start the [!INCLUDEssNoVersion] Browser service. For information on configuring the [!INCLUDEssNoVersion] Browser service, see SQL Server Browser Service.

At the time of connection, the [!INCLUDEssNoVersion] Native Client component reads the server, protocol, and port values from the registry for the specified alias name, and creates a connection string in the format tcp:<servername>[\<instancename>],<port> or tcp:<IPAddress>[\<instancename>],<port>.

Note

The [!INCLUDEmsCoName] Windows Firewall closes port 1433 by default. Because [!INCLUDEmsCoName][!INCLUDEssNoVersion] communicates over port 1433, you must reopen the port if [!INCLUDEssNoVersion] is configured to listen for incoming client connections using TCP/IP. For information on configuring a firewall, see "How to: Configure a Firewall for SQL Server Access" in [!INCLUDEssNoVersion] Books Online or review your firewall documentation.

[!INCLUDEssNoVersion] and [!INCLUDEssNoVersion] Native Client fully support both Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). [!INCLUDEssNoVersion] Configuration Manager accepts both IPv4 and IPv6 formats for IP addresses. For information on IPv6, see "Connecting Using IPv6" in [!INCLUDEssNoVersion] Books Online.

Connecting to the Local Server

When connecting to [!INCLUDEssNoVersion] running on the same computer as the client, you can use (local) as the server name. This is not encouraged as it leads to ambiguity, however it can be useful when the client is known to be running on the intended computer. For instance, when creating an application for mobile disconnected users, such as a sales force, where [!INCLUDEssNoVersion] will run on laptop computers and store project data, a client connecting to (local) would always connect to the [!INCLUDEssNoVersion] running on the laptop. The word localhost or a period (.) can be used in place of (local).

Verifying Your Connection Protocol

The following query returns the protocol used for the current connection.

SELECT net_transport   
FROM sys.dm_exec_connections   
WHERE session_id = @@SPID;

Examples

Connecting by server name:

Alias Name         <serveralias>  
Port No            <blank>  
Protocol           TCP/IP  
Server             <servername>

Connecting by server name to a named instance:

Alias Name         <serveralias>  
Port No            <blank>  
Protocol           TCP/IP  
Server             <servername>\<instancename>

Connecting by server name to a specified port:

Alias Name         <serveralias>  
Port No            <port>  
Protocol           TCP/IP  
Server             <servername>

Connecting by IP address:

Alias Name         <serveralias>  
Port No            <blank>  
Protocol           TCP/IP  
Server             <IPAddress>

Connecting by IP address to a named instance:

Alias Name         <serveralias>  
Port No            <blank>  
Protocol           TCP/IP  
Server             <IPAddress>\<instancename>

Connecting by IP address to a specified port:

Alias Name         <serveralias>  
Port No            <port number>  
Protocol           TCP/IP  
Server             <IPAddress>

Connecting to the local computer using (local):

Alias Name         <serveralias>  
Port No            <blank>  
Protocol           TCP/IP  
Server             (local)

Connecting to the local computer using localhost:

Alias Name         <serveralias>  
Port No            <blank>  
Protocol           TCP/IP  
Server             localhost

Connecting to a named instance on the local computer localhost:

Alias Name         <serveralias>  
Port No            <blank>  
Protocol           TCP/IP  
Server             localhost\<instancename>

Connecting to the local computer using a period:

Alias Name         <serveralias>  
Port No            <blank>  
Protocol           TCP/IP  
Server             .

Connecting to a named instance on the local computer using a period:

Alias Name         <serveralias>  
Port No            <blank>  
Protocol           TCP/IP  
Server             .\<instancename>

Note

For information on specifying the network protocol as a sqlcmd parameter, see "How to: Connect to the Database Engine Using sqlcmd.exe" in [!INCLUDEssNoVersion] Books Online.

See Also

Creating a Valid Connection String Using Shared Memory Protocol
Creating a Valid Connection String Using Named Pipes
Choosing a Network Protocol