SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Named Pipes vs. TCP/IP Sockets, Which One?


Named Pipes vs. TCP/IP Sockets, Which One?

Author
Message
Allen Cui-55137
Allen Cui-55137
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3541 Visits: 1
Named Pipes or TCP/IP Sockets used for client to connect to SQL Server in local area network environment, ie client and server are in separate machines, which one do you perfer to use? Why?



SQLBill
SQLBill
SSCarpal Tunnel
SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)

Group: General Forum Members
Points: 4977 Visits: 1077
We use TCP/IP.

This is from Inside Microsoft SQL Server 2000 by Kalen Delaney.

quote:
Microsoft internal testing has found the TCP/IP Sockets Net-Library to be the fastest networking choice, although in a typical LAN you rarely see the network as a performanc bottleneck. In a low-speed WAN, however, this can be an important issue. Some network administrators have also been concerned about potentially reouting NetBIOS traffic across their LANs and WANs. However, if SQL Serve is not using the Named Pipes Net-Library and the Multiprotocol Net-Library is not using named pipes under the covers for IPC, SQL Server is not using NetBIOS at all and this is not a concern.


I have also seen comments elsewhere that TCP/IP is better for security.

-SQLBill



Steven.
Steven.
SSC Eights!
SSC Eights! (917 reputation)SSC Eights! (917 reputation)SSC Eights! (917 reputation)SSC Eights! (917 reputation)SSC Eights! (917 reputation)SSC Eights! (917 reputation)SSC Eights! (917 reputation)SSC Eights! (917 reputation)

Group: General Forum Members
Points: 917 Visits: 247
I have found that tcp-ip has less connection issues, espically now with ms03-031 restricting named-pipe access (Q823492)

Steven
Thomas Rushton
Thomas Rushton
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: Moderators
Points: 3277 Visits: 3341
We use TCP/IP. We've also found it to be more reliable than Named Pipes.
satishbt
satishbt
SSC Journeyman
SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)

Group: General Forum Members
Points: 76 Visits: 10
Well, what I have abserved is that if you are trying to connect to a server which resides in another LAN, often noticed that connection via Named Pipes fails and TCP/IP goes thru. There are times when Named Pipe within the LAN fails where TCP/IP goes thru.



satishbt
satishbt
SSC Journeyman
SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)

Group: General Forum Members
Points: 76 Visits: 10
Well, what I have abserved is that if you are trying to connect to a server which resides in another LAN, often noticed that connection via Named Pipes fails and TCP/IP goes thru. There are times when Named Pipe within the LAN fails where TCP/IP goes thru.



satishbt
satishbt
SSC Journeyman
SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)SSC Journeyman (76 reputation)

Group: General Forum Members
Points: 76 Visits: 10
Well, what I have abserved is that if you are trying to connect to a server which resides in another LAN, often noticed that connection via Named Pipes fails and TCP/IP goes thru. There are times when Named Pipe within the LAN fails where TCP/IP goes thru.



cneuhold
cneuhold
SSC Veteran
SSC Veteran (295 reputation)SSC Veteran (295 reputation)SSC Veteran (295 reputation)SSC Veteran (295 reputation)SSC Veteran (295 reputation)SSC Veteran (295 reputation)SSC Veteran (295 reputation)SSC Veteran (295 reputation)

Group: General Forum Members
Points: 295 Visits: 13
hi!

depending on how "clean" your SMB network is set up, we've found TCP/IP more efficient when it comes to network resources, means, whenever possible we use TCP/IP to avoid all the NetBIOS overhead. named pipes is our "fallback" if TCP/IP won't work (eg. weird windows network configuration issues, like no wins server and LM resolution on, means, something you'd never expect to find in the "wild" ;-)

best regards,
chris



robinhc
robinhc
SSC-Enthusiastic
SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)

Group: General Forum Members
Points: 143 Visits: 116
I heard a story about a guy who set up his ODBC in his DMZ using TCP and then disabled NETBEUI to protect against Worms. (or was it NetBIOS?) Does that sound feasible or is this a tall tale.



Arvind-57714
Arvind-57714
SSC Veteran
SSC Veteran (259 reputation)SSC Veteran (259 reputation)SSC Veteran (259 reputation)SSC Veteran (259 reputation)SSC Veteran (259 reputation)SSC Veteran (259 reputation)SSC Veteran (259 reputation)SSC Veteran (259 reputation)

Group: General Forum Members
Points: 259 Visits: 11
TCP/IP is better than Named Pipes any day...owing to the performance and security.

Cheers!

Arvind


Arvind
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search