Skip to content

client-network-configuration.md

Latest commit

 

History

History
71 lines (48 loc) · 7.11 KB

client-network-configuration.md

File metadata and controls

71 lines (48 loc) · 7.11 KB
title Client Network Configuration
description Find out how client computers connect to an instance of SQL Server on a network. Learn about the tools that you can use to manage clients.
author rwestMSFT
ms.author randolphwest
ms.date 08/26/2025
ms.service sql
ms.subservice configuration
ms.topic conceptual
helpviewer_keywords
client configuration [SQL Server], connections
Database Engine [SQL Server], network configurations
connections [SQL Server], client configuration
client connections [SQL Server], about client network connections
client computers [SQL Server]
client connections [SQL Server]
network connections [SQL Server], client configuration

Client network configuration

[!INCLUDE SQL Server]

Client software enables client computers to connect to an instance of [!INCLUDE ssNoVersion] on a network. A "client" is a front-end application that uses the services provided by a server such as the [!INCLUDE ssDEnoversion]. The computer that hosts this application is referred to as the client computer.

At the simplest level, a [!INCLUDE ssNoVersion] client can reside on the same machine as an instance of [!INCLUDE ssNoVersion]. Typically, however, a client connects to one or more remote servers over a network. The client/server architecture of [!INCLUDE ssNoVersion] allows it to seamlessly manage multiple clients and servers on a network. The default client configurations suffice in most situations.

[!INCLUDE ssNoVersion] clients can include applications of various types, such as:

  • OLE DB consumers

    These applications use the [!INCLUDE ssNoVersion] Native Client OLE DB provider to connect to an instance of [!INCLUDE ssNoVersion]. The OLE DB provider mediates between [!INCLUDE ssNoVersion] and client applications that consume [!INCLUDE ssNoVersion] data as OLE DB rowsets. The sqlcmd command prompt utility and [!INCLUDE ssManStudioFull] are examples of OLE DB applications.

  • ODBC applications

    These applications include client utilities installed with previous versions of [!INCLUDE ssNoVersion], such as the osql command prompt utility, and other applications that use the [!INCLUDE ssNoVersion] Native Client ODBC driver to connect to an instance of [!INCLUDE ssNoVersion].

  • DB-Library clients

    These applications include the [!INCLUDE ssNoVersion] isql command prompt utility and clients written to DB-Library. [!INCLUDE ssNoVersion] support for client applications using DB-Library is limited to [!INCLUDE ssNoVersion] 7.0 features.

Note

Although the [!INCLUDE ssDEnoversion] still supports connections from existing applications using the DB-Library and Embedded SQL APIs, it doesn't include the files or documentation needed to do programming work on applications that use these APIs. A future version of the [!INCLUDE ssDEnoversion] will drop support for connections from DB-Library or Embedded SQL applications. Don't 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. [!INCLUDE ssNoVersion] doesn't 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 [!INCLUDE ssNoVersion] version 6.5, [!INCLUDE ssNoVersion] 7.0, or [!INCLUDE ssVersion2000].

Regardless of the type of application, managing a client consists mainly of configuring its connection with the server components of [!INCLUDE ssNoVersion]. 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 [!INCLUDE ssNoVersion] Native Client DLL contains the network libraries and is installed by the setup program. The network protocols aren't enabled during setup for new installations of [!INCLUDE ssNoVersion]. 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 [!INCLUDE ssNoVersion] clients:

  • [!INCLUDE ssNoVersion] Configuration Manager

    Both client and server network components are managed with [!INCLUDE ssNoVersion] Configuration Manager, which combines the [!INCLUDE ssNoVersion] Network Utility, [!INCLUDE ssNoVersion] Client Network Utility, and Service Manager of previous versions. [!INCLUDE ssNoVersion] Configuration Manager is a [!INCLUDE msCoName] 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 [!INCLUDE ssNoVersion] Configuration Manager.

  • Setup

    Run [!INCLUDE ssNoVersion] 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.

In this section

Related content