Named Pipes

I have a SQL Server 2000 Enterprise Edition database with a Windows 2000
operating system. The Client Network Utility the protocols that are Enabled
are TCP/IP and Named Pipes.
TCP/IP is the first protocol in the list and second is Named Pipes.
Could Named Pipes in the Enable protocol list slow down the database or
connection performance?
Thank You,If it's just the fact that the Named Pipes protocol is enabled, there
shouldn't be any performance implication. If you are talking about the
performance implication of using named pipes vs. using TCP/IP, I'm not aware
of any significant difference as of late, although there were some references
in the past (well, way back) about named pipes being less performant in some
cases (see http://support.microsoft.com/?kbid=156430 for an example. Note
that it's last reviewed in 2003)
In general, I prefer TCP/IP not because of any performance implication, but
for administrative convenience. For instance, names pipes depend on NetBIOS,
and require more ports through a firewall.
Linchi
"Joe K." wrote:
> I have a SQL Server 2000 Enterprise Edition database with a Windows 2000
> operating system. The Client Network Utility the protocols that are Enabled
> are TCP/IP and Named Pipes.
> TCP/IP is the first protocol in the list and second is Named Pipes.
> Could Named Pipes in the Enable protocol list slow down the database or
> connection performance?
> Thank You,
>