en:servercommunicationtypes
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
en:servercommunicationtypes [2020/09/28 13:18] – created onyxadmin | en:servercommunicationtypes [2022/01/15 08:21] (current) – onyxadmin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ~~NOTOC~~ | + | |
- | ===== TCP/IP vs. Named Pipes ===== | + | ====== TCP/IP vs. Named Pipes ====== |
---- | ---- | ||
- | In a fast local area network (LAN) environment, | + | In a fast local area network (LAN) environment, |
- | For named pipes, network communications are typically more interactive. A peer does not send data until another peer asks for it using a read command. A network read typically involves a series of peek named pipes messages before it begins to read the data. These can be very costly in a slow network and cause excessive network traffic, which in turn affects other network clients. | + | {{:tcpipe1.png?& |
- | It is also important to clarify if you are talking about local pipes or network | + | ====TCP/ |
+ | For TCP/IP Sockets, data transmissions | ||
+ | TCP/IP Sockets also support a backlog queue, which can provide a limited smoothing effect compared to named pipes that may lead to pipe busy errors when you are attempting to connect to SQL Server.\\ | ||
- | For TCP/IP Sockets, data transmissions | + | ====Named Pipes==== |
+ | For named pipes, network communications | ||
+ | It is also important to clarify if you are talking about local pipes or network pipes. If the server application is running locally | ||
- | TCP/IP Sockets also support a backlog queue, which can provide | + | In general, sockets are preferred in a slow LAN, WAN, or dial-up network, whereas |
- | In general, sockets are preferred in a slow LAN, WAN, or dial-up network, whereas named pipes can be a better choice when network speed is not the issue, as it offers more functionality, | + | ---- |
en/servercommunicationtypes.1601291926.txt.gz · Last modified: 2020/09/28 13:18 by onyxadmin