Labels

What Is The Difference Between TCP/IP And Named Pipes; Interview Question




I was planning to write this post from a very long time and today i was able to post it. Thanks to my mentors who have helped me to understand these protocols in detail.



Sno.
TCP /IP
Named Pipes
1 TCP/IP is preferred in a slow LAN, WAN, or dial-up network This can be a better choice when network speed is not the issue
2 This can be very helpful in a slow network These can be very costly in a slow network and cause excessive network traffic
3 TCP/IP is tough to configure, But its now builtin in many applications It offers more functionality, ease of use, and configuration options
4 This can provide a limited smoothing effect compared to named pipes  Network read typically involves a series of peek named pipes messages before it starts to read the data
5 In TCP/IP, data transmissions are more streamlined For named pipes, network communications are typically more interactive
6 TCP/IP is Desighned for LAN, WAN, or dial-up network If the server application is running locally on the computer that is running an instance of SQL Server, the local Named Pipes protocol is Good Option
7 TCP\IP is a better set of network libraries in almost all cases Specially where network access to SQL Server is remote client connectivity.It always favor the use of TCP/IP communications over Named Pipes. Local named pipes runs in kernel mode and is very fast on local network. Locally, named pipes are considered to extremely fast and a much better option.
8 In TCP/IP, you should see less chatter with this protocol   Named Pipes connectivity always uses more packets to get the same amount of work done when communicating with remote clients.
9 TCP/IP Sockets also support a backlog queue Named pipes could lead to pipe-busy errors when you are trying to connect to SQL Server
10 you'll see much better performance in cases where VPNs or significant network load come into play Named Pipes protocol also offers high-performance benefits when used by client applications residing on the same box
11 TCP/IP uses TCP stack,In this Application will "listen" on a particular TCP port and respond to any requests it receives on the port. Named Pipes do listen for requests from other peers, this is done by having a pipe address which is in the format of "\.\pipe\sql\query."
12 TCP\IP is a better set of network libraries in almost all cases Specially where network access to SQL Server is remote client connectivity.It always favor the use of TCP/IP communications over Named Pipes. Local named pipes runs in kernel mode and is very fast on local network. Locally, named pipes are considered to extremely fast and a much better option.
13 Data transmissions can also take advantage of TCP/IP Sockets performance enhancement mechanisms such as windowing, delayed acknowledgements Performance depend on  local pipes or network pipes
14 For forcing TCP/IP connections use an IP address (instead of a host-name) as the data source within your connection strings, or pre-pend "tcp:" to the front of your host names in the data source section of your connection string For forcing Named pipe connections pre-pend "NP:" to the front of your host names in the data source section of your connection string
15 Tcp/IP conitiniously sends data A peer does not send data until another peer asks for it using a read command


Must Read:











No comments:
Write comments

Please do not enter spam links

Services

More Services