INF: Network Library in Existing DSN Replaced by Network Library in New DSN to the Same SQL Server Name

Article translations Article translations
Article ID: 257434 - View products that this article applies to.
This article was previously published under Q257434
Expand all | Collapse all

On This Page


In ODBC, when you use multiple data source names (DSNs) to connect to the same SQL Server server (and you use the same server name), the most recent DSN's Network Library replaces the Network Libraries in other DSNs.


There is only one Network Library entry under each SQL Server server name in the following registry key:

Hkey_local_machine/Software/Microsoft/MSSQLServer/Client/Connect to

When a new DSN is created for the same SQL Server server, the existing Network Library under this registry entry is replaced by the Network Library used in the new DSN.

Steps to Reproduce Behavior

For example:
  1. Open Control Panel. In the Control Panel dialog box, double-click ODBC Data Sources.
  2. Create a DSN named DSN01, which uses named pipes, to connect to a SQL Server server named TestServer.
  3. Create a second DSN named DSN02, that uses TCP/IP to connect to the same SQL Server server (TestServer).
  4. In the ODBC Data Source Administrator dialog box, select DSN01, and then click Configure.
  5. In the Microsoft SQL Server DSN Configuration dialog box, click Next. Click Client Configuration. In the Add Network Library Configuration dialog box, note that the Network Library has changed TCP/IP.
To use a specific Network Library to connect to SQL Server, you can set up an alias by using the Client Network Utility.


Article ID: 257434 - Last Review: November 14, 2003 - Revision: 3.3
  • Microsoft SQL Server 6.5 Standard Edition
  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft SQL Server 2000 Standard Edition
kbinfo KB257434

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from