Re: Connect to SQL Sererv thru Named Pipes



In message <#O4Jmn8cFHA.2552@xxxxxxxxxxxxxxxxxxxx>, Aruna Tennakoon <aruna.tennakoon@xxxxxxxxx> writes
Hi guys,

Ijust wanted to know how to configure the SQL Server to use Named Pipes and
to acced SQL Server via  Named Pipes from VB 6.

Thanks for your time,
-Aruna

SQL Server and MSDE both install by default with Named Pipes activated (its their default protocol). In order to use TCP/IP protocols you need to specify at install time, or use Enterprise Manager to change, or use Network Tools to change.


Any DSN, ODBC or OLEDB connection string used to connect to SQL Server will default to using named pipes unless you tell it otherwise using the "Network Library" parameter. For example:

Provider=sqloledb;Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=pubs;User ID=sa;Password=asdasd;

The DBMSSOCN tell the OLEDB driver to use TCP/IP instead of the default named pipes (). Other choices for this parameter include:

Name                    Network library
dbnmpntw        -       Win32 Named Pipes
dbmssocn        -       Win32 Winsock TCP/IP
dbmsspxn        -       Win32 SPX/IPX
dbmsvinn        -       Win32 Banyan Vines
dbmsrpcn        -       Win32 Multi-Protocol (Windows RPC)

There are pros and cons as normal for which protocol to use however IMO anything that is not standalone on a single PC you would be better using TCP/IP for speed, performance and flexability. Check out http://www.connectionstrings.com for more ideas on connection strings.

Kind Regards,

--
Andrew D. Newbould                  E-Mail:  newsgroups@xxxxxxxxxxxxxxxxx

ZAD Software Systems                Web   :  www.zadsoft.com
.



Relevant Pages

  • RE: SQLOLEDB always uses Named Pipes
    ... The order is tcp np. ... Disabling Named Pipes in the client configuration utility allowed dbnetlib ... So what exactly does disabling a protocol achieve, ... Is prefixing the server with tcp: the preferred means to request a tcp/ip ...
    (microsoft.public.data.oledb)
  • Re: Umstieg von Access auf SQL-Server
    ... > Bei Port 1433 sabber ich dann immer gleich Named Pipes. ... Nein, TCP/IP. ... How To Change SQL Server Default Network Library Without ... How To Set the SQL Server Network Library in an ADO Connection String ...
    (microsoft.public.de.vb.datenbank)
  • Re: SQL 2008 vs 2005 performance issue
    ... Named Pipes is third in the order of network protocols. ... The SQL Server 2005 machine is using TCP/IP. ... The SQL Server 2008 machine is using Named Pipes. ... I installed SQL Server 2008 Enterprise Eval on my new Toshiba Centrino Duo ...
    (microsoft.public.sqlserver.setup)
  • Re: sql server2000; TCP/IP vs Named Pipes
    ... wireshark.org have an excellent protocol analyser. ... My company is running an application that uses sql server 2000 sp3. ... We prefer to use TCP/IP but we are having issues with users losing there ... How can I isolate the problem to th network? ...
    (microsoft.public.sqlserver.tools)
  • Re: ?? Turning Off TCP/IP Client Has No Effect ??
    ... Did you stop and restart the service after disabling TCP/IP ... My setup involves a single machine running "SQL Server Express 2005". ... SSE includes the "SQL Server Native Client". ... when I run SQLCMD (specifying "tcp:" as the protocol) I am still ...
    (microsoft.public.sqlserver.connect)