Named Pipes v. TCP/IP?
-
Is there anyone able to help me out here? I am looking for the differences between Named Pipes, and TCP/IP connectivity between client and SQL Server. Anything would be great!
-
Named Pipes is specific to Microsoft and if the Cleint and Server are on the
same machine, MicroSoft uses Named Pipes. TCP/IP has more overheads
but is the best when client/servers are distributed.
Gopi
-
Oh, thanks! I was searching, and no where that I was looking really compared the two to each other...
-
hi vanessa
i hope this link can reply your question.
-
Grajee - named pipes is not only for when clinet and server are on same machine (though it is most efficient in this mode) - actually it is a crude mechanism that uses a shared file to pass the info (it is also not MS only as it is based on old IBM netbios standard). In general TCP/IP is much faster for networked clients but if client and server are on the same box then named pipes is not too bad as the shared directory is then local to both.
James Horsley
Workflow Consulting Limited -
The following links are useful in this regard
BOL : Namedpipes Vs Tcp/Ip sockets
http://www.rlisolutions.com/article/96/sql-server-connection-clients
Rafi-
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply