Connecting to the SQL Server Database Engine
Connecting to the Microsoft SQL Server Database Engine includes five elements.
- Installing network protocols on the server and client computers.
Network protocols are a feature of the operating system and are installed and configured using Microsoft Windows tools. For information about installing and configuring network protocols, see your Windows documentation, or contact your network administrator. - Enabling and configuring the Database Engine to listen on one or more network protocols.
Use the SQL Server Configuration Manager, to enable the protocols you wish to use. For more information, see Server Network Configuration. When enabled, the Database Engine receives database communication from client computers formatted by the SQL Native Client. The SQL Native Client is normally installed on the server as well, for use by the local SQL Server tools. - Installing the SQL Native Client on each client computer.
SQL Native Client (SQLNCLI) is a data access technology that is new to Microsoft SQL Server 2005, and it is a stand-alone data access Application Programming Interface (API) that is used for both OLE DB and ODBC. It combines the SQL OLE DB Provider and the SQL ODBC Driver into one native dynamic link library (DLL) while also providing new functionality that is separate and distinct from the Microsoft Data Access Components (MDAC). Use SQL Server Setup to install SQLCLI as part of the SQL Server 2005 Tools. For more information about Net-Libraries, see Network Protocols, and TDS Endpoints. - Enabling and configuring each client computer to connect using the desired protocol.
After installation, use SQL Server Configuration Manager to enable protocols, and designate the order in which protocols are used when attempting a connection. For more information, see Client Network Configuration. - Opening ports in the firewall to permit database communication.
- Use a proxy server to connect to an instance of SQL Server. For more information, see Connecting to SQL Server Through a Proxy Server.
- Use a firewall system to isolate the network containing the instance of SQL Server from the rest of the Internet. For more information, see Connecting to SQL Server over the Internet.
In This Section
| Topic | Description |
|---|---|
Contains information about server network configuration tasks such as enabling protocols, modifying the port or pipe used by a protocol, configuring encryption, configuring the SQL Server Browser service, exposing or hiding the SQL Server Database Engine on the network, and registering the Server Principal Name. |
|
Describes installing SQL Native Client Net-Libraries on the server and client computers and enabling a matching pair of network protocols. |
|
Contains information about how to connect client computers to an instance of SQL Server 2005 on a network. |
|
Describes using Microsoft Internet Security and Acceleration (ISA) Server to connect to an instance of Microsoft SQL Server. |
|
Describes using the Internet to connect to an instance of Microsoft SQL Server Database Engine using SQL Server Management Studio or a client application based on OLE DB, or Open Database Connectivity (ODBC). |
See Also
Other Resources
SQL Server Configuration Manager
SQL Native Client Programming