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'm not sure that's a fair characterization of TCP/IP
> 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?
>
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:|||In the Book Inside SQL Server 7.0 , it is mentioned that TCP/IP is the
>news:021701c3d11a$a3d6e3f0$a001280a@.phx.gbl...
why[QUOTE]
>
>.
>
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.
