5 replies
by rickh9
Named Pipes is definately slower than TCP/IP due to added encription features etc. However the difference is usually slight and other factors such as database design, indexes etc. tend to have more of an effect. There are some documented bugs (access) that will slam your network, as well as several security issues when using named pipes. A quick search on microsoft technet should return a few articles on the known issues.
As far as real world goes, we do use a few minor apps in which named pipes has been left the default. On our primary Client\Server App we were forced to change to TCP due to periodic network crashes and poor performance in general. Since this was an app. that we have no design control over it was much simpler to drop the pipes. Crashes gone and about a 20% overall improvement in performance.
by mrkellam
by not_a_geek
by mrkellam
by mrkellam
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending