Client Network Configuration
Applies to: SQL Server (all supported versions)
Client software enables client computers to connect to an instance of Microsoft SQL Server on a network. A «client» is a front-end application that uses the services provided by a server such as the SQL Server Database Engine. The computer that hosts this application is referred to as the client computer.
At the simplest level, a SQL Server client can reside on the same machine as an instance of SQL Server. Typically, however, a client connects to one or more remote servers over a network. The client/server architecture of SQL Server allows it to seamlessly manage multiple clients and servers on a network. The default client configurations suffice in most situations.
SQL Server clients can include applications of various types, such as:
OLE DB consumers
These applications use the SQL Server Native Client OLE DB provider to connect to an instance of SQL Server. The OLE DB provider mediates between SQL Server and client applications that consume SQL Server data as OLE DB rowsets. The sqlcmd command prompt utility and SQL Server Management Studio, are examples of OLE DB applications.
These applications include client utilities installed with previous versions of SQL Server, such as the osql command prompt utility, as well as other applications that use the SQL Server Native Client ODBC driver to connect to an instance of SQL Server.
These applications include the SQL Server isql command prompt utility and clients written to DB-Library. SQL Server support for client applications using DB-Library is limited to Microsoft SQL Server 7.0 features.
Although the SQL Server Database Engine still supports connections from existing applications using the DB-Library and Embedded SQL APIs, it does not include the files or documentation needed to do programming work on applications that use these APIs. A future version of the SQL Server Database Engine will drop support for connections from DB-Library or Embedded SQL applications. Do not use DB-Library or Embedded SQL to develop new applications. Remove any dependencies on either DB-Library or Embedded SQL when modifying existing applications. Instead of these APIs, use the SQLClient namespace or an API such as OLE DB or ODBC. SQL Server does not include the DB-Library DLL required to run these applications. To run DB-Library or Embedded SQL applications you must have available the DB-Library DLL from SQL Server version 6.5, SQL Server 7.0, or SQL Server 2000 (8.x).
Regardless of the type of application, managing a client consists mainly of configuring its connection with the server components of SQL Server. Depending on the requirements of your site, client management can range from little more than entering the name of the server computer to building a library of custom configuration entries to accommodate a diverse multiserver environment.
The SQL Server Native Client DLL contains the network libraries and is installed by the setup program. The network protocols are not enabled during setup for new installations of SQL Server. Upgraded installations enable the previously enabled protocols. The underlying network protocols are installed as part of Windows Setup (or through Networks in Control Panel). The following tools are used to manage SQL Server clients:
SQL Server Configuration Manager
Both client and server network components are managed with SQL Server Configuration Manager, which combines the SQL Server Network Utility, SQL Server Client Network Utility, and Service Manager of previous versions. SQL Server Configuration Manager is a Microsoft Management Console (MMC) snap-in. It also appears as a node in the Windows Computer Manager snap-in. Individual network libraries can be enabled, disabled, configured, and prioritized using SQL Server Configuration Manager.
Run SQL Server setup to install the network components on a client computer. Individual network libraries can be enabled or disabled during setup when Setup is started from the command prompt.
ODBC Data Source Administrator
The ODBC Data Source Administrator lets you create and modify ODBC data sources on computers running the Microsoft Windows operating system.
Конфигурация клиентской сети Client Network Configuration
Применимо к: Applies to: SQL Server SQL Server (все поддерживаемые версии) SQL Server SQL Server (all supported versions) Применимо к: Applies to: SQL Server SQL Server (все поддерживаемые версии) SQL Server SQL Server (all supported versions)
Программное обеспечение клиента дает возможность клиентским компьютерам подключаться к экземпляру Microsoft Microsoft SQL Server SQL Server по сети. Client software enables client computers to connect to an instance of Microsoft Microsoft SQL Server SQL Server on a network. «Клиент» — это клиентская часть приложения, использующая службы, предоставленные сервером, например Компонент SQL Server Database Engine SQL Server Database Engine . A «client» is a front-end application that uses the services provided by a server such as the Компонент SQL Server Database Engine SQL Server Database Engine . Компьютер, содержащий это приложение, упоминается как компьютер клиента. The computer that hosts this application is referred to as the client computer.
В простейшем случае клиент SQL Server SQL Server может находиться на том же самом компьютере, где находится экземпляр SQL Server SQL Server . At the simplest level, a SQL Server SQL Server client can reside on the same machine as an instance of SQL Server SQL Server . Однако обычно клиент подключается к одному или более удаленным серверам через сеть. Typically, however, a client connects to one or more remote servers over a network. Архитектура клиент-сервер SQL Server SQL Server позволяет ему прозрачно управлять множеством клиентов и серверов в сети. The client/server architecture of SQL Server SQL Server allows it to seamlessly manage multiple clients and servers on a network. Конфигурации клиента по умолчанию достаточно для большинства ситуаций. The default client configurations suffice in most situations.
SQL Server SQL Server могут включать приложения различных типов, например: clients can include applications of various types, such as:
Потребители OLE DB OLE DB consumers
Эти приложения подключаются к экземпляру SQL Server SQL Server с помощью поставщика OLE DB для собственного клиента SQL Server SQL Server . These applications use the SQL Server SQL Server Native Client OLE DB provider to connect to an instance of SQL Server SQL Server . Поставщик OLE DB является посредником между SQL Server SQL Server и приложениями клиента, которые потребляют данные SQL Server SQL Server как набор строк OLE DB. The OLE DB provider mediates between SQL Server SQL Server and client applications that consume SQL Server SQL Server data as OLE DB rowsets. Служебная программа командной строки sqlcmd и SQL Server Management Studio SQL Server Management Studio — это примеры приложений OLE DB. The sqlcmd command prompt utility and SQL Server Management Studio SQL Server Management Studio , are examples of OLE DB applications.
Приложения ODBC ODBC applications
Эти приложения включают клиентские программы, установленные с предыдущими версиями SQL Server SQL Server , такие как программа командной строки osql , а также другие приложения, которые используют драйвер ODBC SQL Server SQL Server Native Client для подключения к экземпляру SQL Server SQL Server . These applications include client utilities installed with previous versions of SQL Server SQL Server , such as the osql command prompt utility, as well as other applications that use the SQL Server SQL Server Native Client ODBC driver to connect to an instance of SQL Server SQL Server .
Клиенты DB-Library DB-Library clients
Эти приложения включают программу командной строки SQL Server SQL Server isql и клиенты, написанные для DB-Library. These applications include the SQL Server SQL Server isql command prompt utility and clients written to DB-Library. Поддержка SQL Server SQL Server для клиентских приложений, использующих DB-Library, ограничена функциями Microsoft Microsoft SQL Server SQL Server 7.0. SQL Server SQL Server support for client applications using DB-Library is limited to Microsoft Microsoft SQL Server SQL Server 7.0 features.
Хотя компонент Компонент SQL Server Database Engine SQL Server Database Engine до сих пор поддерживает соединения из существующих приложений, использующих API-интерфейсы DB-Library и Embedded SQL, файлы или документация, необходимые для разработки приложений с использованием этих API, не предоставляются. Although the Компонент SQL Server Database Engine SQL Server Database Engine still supports connections from existing applications using the DB-Library and Embedded SQL APIs, it does not include the files or documentation needed to do programming work on applications that use these APIs. В следующей версии компонента Компонент SQL Server Database Engine SQL Server Database Engine не будут поддерживаться соединения приложений DB-Library или Embedded SQL. A future version of the Компонент SQL Server Database Engine SQL Server Database Engine will drop support for connections from DB-Library or Embedded SQL applications. Не используйте DB-Library или Embedded SQL для разработки новых приложений. Do not use DB-Library or Embedded SQL to develop new applications. Удалите все зависимости от DB-Library или Embedded SQL при модификации существующих приложений. Remove any dependencies on either DB-Library or Embedded SQL when modifying existing applications. Вместо этих API используйте пространство имен SQLClient или такой API, как OLE DB или ODBC. Instead of these APIs, use the SQLClient namespace or an API such as OLE DB or ODBC. SQL Server SQL Server не включает DB-Library DLL, необходимую для выполнения этих приложений. does not include the DB-Library DLL required to run these applications. Для запуска приложений DB-Library или Embedded SQL необходимо иметь доступ к DLL-библиотеке DB-Library для SQL Server SQL Server 6.5, SQL Server SQL Server 7.0 или SQL Server 2000 (8.x) SQL Server 2000 (8.x) . To run DB-Library or Embedded SQL applications you must have available the DB-Library DLL from SQL Server SQL Server version 6.5, SQL Server SQL Server 7.0, or SQL Server 2000 (8.x) SQL Server 2000 (8.x) .
Управление клиентом заключается главным образом в настройке его подключения к компонентам сервера SQL Server SQL Server — независимо от типа приложения. Regardless of the type of application, managing a client consists mainly of configuring its connection with the server components of SQL Server SQL Server . В зависимости от требований сайта управление клиентами может варьироваться от небольшого числа операций после ввода имени сервера до построения библиотеки записей пользовательских конфигураций, чтобы обеспечить соответствие в разнообразной среде с несколькими серверами. Depending on the requirements of your site, client management can range from little more than entering the name of the server computer to building a library of custom configuration entries to accommodate a diverse multiserver environment.
DLL-файл собственного клиента SQL Server SQL Server содержит сетевые библиотеки и устанавливается программой установки. The SQL Server SQL Server Native Client DLL contains the network libraries and is installed by the setup program. Сетевые протоколы не включаются во время установки новых экземпляров SQL Server SQL Server . The network protocols are not enabled during setup for new installations of SQL Server SQL Server . При обновлении экземпляров включаются предварительно включенные протоколы. Upgraded installations enable the previously enabled protocols. Основные сетевые протоколы устанавливаются как часть установки Windows (или через элемент «Сетевые подключения» панели управления). The underlying network protocols are installed as part of Windows Setup (or through Networks in Control Panel). Следующие инструменты используются для управления клиентами SQL Server SQL Server . The following tools are used to manage SQL Server SQL Server clients:
SQL Server SQL Server Configuration Manager Configuration Manager
И клиент, и компоненты сети сервера управляются с помощью диспетчера конфигурации SQL Server SQL Server , который объединяет программу сети SQL Server SQL Server , программу сети клиента SQL Server SQL Server и диспетчер служб предыдущих версий. Both client and server network components are managed with SQL Server SQL Server Configuration Manager, which combines the SQL Server SQL Server Network Utility, SQL Server SQL Server Client Network Utility, and Service Manager of previous versions. SQL Server SQL Server Диспетчер конфигурации является оснасткой консоли управления Microsoft Microsoft (MMC). Configuration Manager is a Microsoft Microsoft Management Console (MMC) snap-in. Кроме того, он отображается как узел в оснастке Windows «Управление компьютером». It also appears as a node in the Windows Computer Manager snap-in. С помощью диспетчера конфигурации SQL Server SQL Server отдельные сетевые библиотеки можно включить, отключить, настроить и упорядочить по приоритету. Individual network libraries can be enabled, disabled, configured, and prioritized using SQL Server SQL Server Configuration Manager.
Запустите программу установки SQL Server SQL Server и установите сетевые компоненты на компьютере клиента. Run SQL Server SQL Server setup to install the network components on a client computer. Отдельные сетевые библиотеки могут быть включены или отключены во время установки, когда установка начата из командной строки. Individual network libraries can be enabled or disabled during setup when Setup is started from the command prompt.
Администратор источников данных ODBC ODBC Data Source Administrator
С помощью администратора источников данных ODBC можно создавать и изменять источники данных ODBC на компьютерах, работающих под управлением операционной системы Microsoft Windows. The ODBC Data Source Administrator lets you create and modify ODBC data sources on computers running the Microsoft Windows operating system.
Configure Client Protocols
Applies to: SQL Server (all supported versions)
This topic describes how to configure client protocols used by client applications in SQL Server by using SQL Server Configuration Manager. Microsoft SQL Server supports client communication with the TCP/IP network protocol and the named pipes protocol. The shared memory protocol is also available if the client is connecting to an instance of the Database Engine on the same computer. There are three common methods of selecting the protocol.
Configure all client applications to use the same network protocol by setting the protocol order in SQL Server Configuration Manager.
Configure a single client application to use a different network protocol by creating an alias. For more information, see Create or Delete a Server Alias for Use by a Client (SQL Server Configuration Manager).
Some client applications, such as sqlcmd.exe, can specify the protocol as part of the connection string. For more information, see Connect to the Database Engine With sqlcmd.
Using SQL Server Configuration Manager
To enable or disable a client protocol
In SQL Server Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then click Properties.
Click a protocol in the Disabled Protocols box, and then click Enable, to enable a protocol.
Click a protocol in the Enabled Protocols box, and then click Disable, to disable a protocol.
To change the default protocol or the protocol order for client computers
In SQL Server Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then click Properties.
In the Enabled Protocols box, click Move Up or Move Down, to change the order in which protocols are tried, when attempting to connect to SQL Server. The top protocol in the Enabled Protocols box is the default protocol.
SQL Server Configuration Manager creates registry entries for the server alias configurations and default client network library. However, the application does not install either the SQL Server client network libraries or the network protocols. The SQL Server client network libraries are installed during SQL Server Setup; the network protocols are installed as part of Microsoft Windows Setup (or through Networks in Control Panel). A particular network protocol may not be available as part of Windows Setup. For more information about installing these network protocols, see the vendor documentation.
To configure a client to use TCP/IP
In SQL Server Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then click Properties.
In the Enabled Protocols box, click the up and down arrows to change the order in which protocols are tried, when attempting to connect to SQL Server. The top protocol in the Enabled Protocols box is the default protocol.
The shared memory protocol is enabled separately by checking the Enabled Shared Memory Protocol box.
