named pipes versus tcpip

Is using the named pipes protocol more/less secure and/or
slower than using tcpip to connect to SQL server?
"Colleen Rossman" <anonymous@.discussions.microsoft.com> wrote in message
news:136401c4aba9$c7ef54b0$a601280a@.phx.gbl...
> Is using the named pipes protocol more/less secure and/or
> slower than using tcpip to connect to SQL server?
Named Pipes is equally secure (ie, vulerable to ethernet sniffing).
In two special cases Named Pipes is faster: on the same machine, and over
local-area networks using the NetBUI protocol. In other cases TCP/IP is
faster, since in those cases Named Pipes would be running _over_ TCP/IP.
Remember that all the client netlibs date from before TCP/IP took over the
world. Back then you would choose the netlib which matched your LAN's
network protocol. Well today every network runs on IP, so everyone uses the
TCP/IP netlib.
David

Named pipes question.

Is it possible to configure named pipes only on one NIC and tcpip on the
other' (SQL 2000 sp3)
PierreNot in SQL 2000. You cannot protocol 'affinitize' NIC's
(Hopefully in the next version)
"Pierre" <Pierre.roman@.qunara.com.nospam> wrote in message
news:%23E0dhpvqDHA.2632@.TK2MSFTNGP09.phx.gbl...
> Is it possible to configure named pipes only on one NIC and tcpip on the
> other' (SQL 2000 sp3)
> Pierre
>|||Thanks
"Dieter Katzenland" <deiter@.rrtc.com> wrote in message
news:uYNs2SwqDHA.2772@.TK2MSFTNGP12.phx.gbl...
> Not in SQL 2000. You cannot protocol 'affinitize' NIC's
> (Hopefully in the next version)
> "Pierre" <Pierre.roman@.qunara.com.nospam> wrote in message
> news:%23E0dhpvqDHA.2632@.TK2MSFTNGP09.phx.gbl...
> > Is it possible to configure named pipes only on one NIC and tcpip on the
> > other' (SQL 2000 sp3)
> >
> > Pierre
> >
> >
>|||Pierre,
Yes, but only with a (software) firewall.
Named pipes use SMB, TCP/IP uses port 1433 (default).
You cannot currently separate the protocols by any binding or SQL setup that I know of.
Regards
AJ
"Pierre" <Pierre.roman@.qunara.com.nospam> wrote in message news:%23E0dhpvqDHA.2632@.TK2MSFTNGP09.phx.gbl...
> Is it possible to configure named pipes only on one NIC and tcpip on the
> other' (SQL 2000 sp3)
> Pierre
>

Named Pipes or TCPIP

I remember reading somewhere that TCPIP gives better
performance than named pipes. Can anyone explain why or
point me in the direction of a tech doc that explains why
we should use TCPIP rather than N/Ps?I'll tell you one drawback of TCP/IP vs Named Pipes. TCP/IP runs on ports,
so if the client is trying to connect on a port the server isn't listening
or if that port is blocked on a firewall, you are in trouble. The default
port is 1433.
Here's the MSDN tech doc link you are looking for:
http://msdn.microsoft.com/library/e...tun_1a_7fcj.asp
Looks like the performance varies on the type of network you are using. I
will tell you Named Pipes is a lot simpler...it is the default, and it
requires no configuration.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:021701c3d11a$a3d6e3f0$a001280a@.phx.gbl...

quote:

---

> I remember reading somewhere that TCPIP gives better
> performance than named pipes. Can anyone explain why or
> point me in the direction of a tech doc that explains why
> we should use TCPIP rather than N/Ps?
>

---

|||I'm not sure that's a fair characterization of TCP/IP
spockets vs. Named pipes.
Just like sockets requiring ports, named pipes require
pipes. In a TCP/IP network, named pipes ultimately require
ports too. When it comes to firewall configurations,
you'll find that the ports (e.g. TCP 139 or TCP 445) used
by the named pipes are more likely to be blocked than the
SQL Server socket port(s).
I don't think named pipes are any simpler than TCP/IP
sockets.
Linchi

quote:

---

>--Original Message--
>I'll tell you one drawback of TCP/IP vs Named Pipes.

---

TCP/IP runs on ports,

quote:

---

>so if the client is trying to connect on a port the

---

server isn't listening

quote:

---

>or if that port is blocked on a firewall, you are in

---

trouble. The default

quote:

---

>port is 1433.
>Here's the MSDN tech doc link you are looking for:
>http://msdn.microsoft.com/library/en-

---

us/optimsql/odp_tun_1a_7fcj.asp

quote:

---

>Looks like the performance varies on the type of network

---

you are using. I

quote:

---

>will tell you Named Pipes is a lot simpler...it is the

---

default, and it

quote:

---

>requires no configuration.
>--
> ****************************************
******************

---

*********

quote:

---

>Andy S.
>MCSE NT/2000, MCDBA SQL 7/2000
>andymcdba1@.NOMORESPAM.yahoo.com
>Please remove NOMORESPAM before replying.
>Always keep your antivirus and Microsoft software
>up to date with the latest definitions and product

---

updates.

quote:

---

>Be suspicious of every email attachment, I will never send
>or post anything other than the text of a http:// link nor
>post the link directly to a file for downloading.
>This posting is provided "as is" with no warranties
>and confers no rights.
> ****************************************
******************

---

*********

quote:

---

>"John" <anonymous@.discussions.microsoft.com> wrote in

---

message

quote:

---

>news:021701c3d11a$a3d6e3f0$a001280a@.phx.gbl...
why[QUOTE]
>
>.
>

---

|||In the Book Inside SQL Server 7.0 , it is mentioned that TCP/IP is the
fastest , (page 78) The same paragraph is also in Chapter 3 of Inside SQL
2000.
However, the bottleneck for most client /server applications is rarely the
network library. Most performance gains
are made by proper design of the database and use of efficient queries.
Also, applications that reside on the same machine as SQL, can take
advantage of local pipes or use Shared Memory
and avoid traffic on the network altogether.
There is no specific doc that states use TCP instead of Named Pipes.
However, we have found that for applications that go across a WAN or
Internet Based Applications typically perform better using TCP/IP. For
applications running on Local Area Networks, changing the network library
doesn't dramatically change the performance of the application.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

name pipe VS tcpip

I found that I can only use name pipe to connect to the sql server.
When I use tcpip, it fails to connect.
I am sure I have enabled the TCP/IP protocol in SQL server
What causes it?
sql is using port no.1433 and I have try using dynamically determine port
and force it to 1433 in ODBC setting.
thank you very much
"!" <!@.!.!> wrote in message news:%236FqHb0qEHA.3416@.TK2MSFTNGP15.phx.gbl...
> I found that I can only use name pipe to connect to the sql server.
> When I use tcpip, it fails to connect.
> I am sure I have enabled the TCP/IP protocol in SQL server
> What causes it?
> sql is using port no.1433 and I have try using dynamically determine port
> and force it to 1433 in ODBC setting.
There are a lot of reasons that this can fail, application type being one of
them. Reference the following as a troubleshooting guide:
http://support.microsoft.com/default...b;en-us;827422
Steve