Export (0) Print
Expand All

Surface Area Configuration for Services and Connections (Remote Connections) - Database Engine

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

By default, SQL Server Express, Evaluation, and Developer editions allow local client connections only. Enterprise, Standard, and Workgroup editions also listen for remote client connections over TCP/IP. Use the Remote Connections page to change the protocols on which SQL Server listens for incoming client connections. TCP/IP is preferred over named pipes because it requires fewer ports to be opened across the firewall.

This settings on the Remote Connections page affect incoming connections only, not outward server connections such as those used for distributed queries.

Note:
You must restart the Database Engine instance's service to apply changes.

Local connections only

If selected, the Database Engine instance will only listen for shared memory connections on the local computer. Connections from remote computers will fail.

Note:
The dedicated administrator connection port is configured separately. See Surface Area Configuration for Features (DAC) - Database Engine.

Local and remote connections

If selected, the Database Engine instance will listen for connections from the local computer and from remote computers using the selected protocols.

Using TCP/IP protocol only

If selected, the Database Engine instance listens for remote connections using TCP/IP, but not named pipes.

Using Named Pipes protocol only

If selected, the Database Engine instance listens for remote connections using named pipes, but not TCP/IP.

Using both TCP/IP and Named Pipes protocols

If selected, the Database Engine instance listens for remote connections using TCP/IP and named pipes.

Show:
© 2014 Microsoft