Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Named Pipes vs. TCP/IP Sockets, Which One? Expand / Collapse
Author
Message
Posted Wednesday, September 24, 2003 11:31 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, November 2, 2005 11:49 AM
Points: 2,611, 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?




Post #16630
Posted Wednesday, September 24, 2003 12:36 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Wednesday, December 17, 2014 12:12 PM
Points: 3,248, Visits: 569
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




Post #80842
Posted Thursday, September 25, 2003 1:24 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Friday, October 17, 2014 3:39 AM
Points: 739, Visits: 212
I have found that tcp-ip has less connection issues, espically now with ms03-031 restricting named-pipe access (Q823492)




Steven
Post #80843
Posted Thursday, September 25, 2003 1:33 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, April 4, 2014 5:29 AM
Points: 965, Visits: 396
We use TCP/IP. We've also found it to be more reliable than Named Pipes.




Post #80844
Posted Thursday, September 25, 2003 2:22 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, February 12, 2009 6:49 AM
Points: 56, 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.




Post #80845
Posted Thursday, September 25, 2003 2:22 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, February 12, 2009 6:49 AM
Points: 56, 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.




Post #80846
Posted Thursday, September 25, 2003 2:26 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, February 12, 2009 6:49 AM
Points: 56, 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.




Post #80847
Posted Thursday, September 25, 2003 3:46 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, August 5, 2013 1:19 AM
Points: 245, 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




Post #80848
Posted Thursday, September 25, 2003 3:25 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, October 26, 2012 9:20 AM
Points: 111, Visits: 112
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.




Post #80849
Posted Friday, September 26, 2003 6:26 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, September 2, 2009 10:26 AM
Points: 229, Visits: 11
TCP/IP is better than Named Pipes any day...owing to the performance and security.

Cheers!

Arvind



Arvind
Post #80850
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse