NCS Logo - Click for home page Northstar Developer Center
Platforms
All Platforms
.NET Framework (1.x - 4.x)
Active Server Pages
ASP.NET
C#
SQL Server
VB.NET
Visual Basic

Keywords
.NET Data Types
.NET E-mail
.NET Events
.NET Functions
.NET Object Programming
.NET System.Configuration
.NET System.Diagnostics
.NET System.IO
.NET System.Net
.NET System.Net.Sockets
Active Data Objects
ASP Architecture
ASP Black Belt
ASP Built-in Functions
ASP Built-in Objects
ASP Debugging
ASP Performance
ASP Security
ASP Syntax
ASP.NET Authentication
ASP.NET Controls
ASP.NET Data Access
ASP.NET Features
ASP.NET Master Pages
ASP.NET Page Events
ASP.NET Security
ASP.NET ViewState
Atom
Certifications
COM, DCOM, COM+
Data Access
E-Mail
Errors
Exporting Data
HTML Tips
IIS
Object-Oriented Programming
RSS
SQL
Uncategorized ASP Tips
VB API Programming
VB Forms
VB Syntax
XML

Book Support
Visual Basic 6 Bible
ASP Bible
ASP Weekend Crash Course
ASP.NET At Work
Creating Web Services

Specifying Network Library for SQL Server

Written by Eric Smith, Northstar Computer Systems LLC

The typical connection string I use for SQL Server looks something like this:
   cnDB.Open "Provider=SQLOLEDB;" _
      & "Data Source=(local);" _
      & "Initial Catalog=Intranet;" _
      & "User ID=sa;" _
      & "Password=sa!;"
In cases where I need to point to another server, there are cases in which I need to specify the network library. Here's how you can do it:
   cnDB.Open "Provider=SQLOLEDB;" _
      & "Data Source=(local);" _
      & "Initial Catalog=Intranet;" _
      & "Network Library=DBMSSOCN;" _
      & "User ID=sa;" _
      & "Password=sa!;"
This specifies that the socket library is to be used for this connection. It's redundant for the same server, but if you need to point from one server to another, it can come in handy. The network libraries that are available are listed in the SQL Client Configuration Utility or the Server Configuration Utility.

Keywords: [ Uncategorized ASP Tips ]

Publication Date: 2/10/2001