diff. between named pipe & TCP-IP

Hi
Is there any diff. between Named Pipe& TCP-IP protocol from performance
point of view there by I can force all the users connecting to server with
TCP-IP proctocol only .
Regards
Ajay RengunthwarFrom BOL:
Named Pipes vs. TCP/IP Sockets
In a fast local area network (LAN) environment, Transmission Control
Protocol/Internet Protocol (TCP/IP) Sockets and Named Pipes clients are
comparable in terms of performance. However, the performance difference
between the TCP/IP Sockets and Named Pipes clients becomes apparent with
slower networks, such as across wide area networks (WANs) or dial-up
networks. This is because of the different ways the interprocess
communication (IPC) mechanisms communicate between peers.
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.
It is also important to clarify if you are talking about local pipes or
network pipes. If the server application is running locally on the computer
running an instance of Microsoft® SQL ServerT 2000, the local Named Pipes
protocol is an option. Local named pipes runs in kernel mode and is
extremely fast.
For TCP/IP Sockets, data transmissions are more streamlined and have less
overhead. Data transmissions can also take advantage of TCP/IP Sockets
performance enhancement mechanisms such as windowing, delayed
acknowledgements, and so on, which can be very beneficial in a slow network.
Depending on the type of applications, such performance differences can be
significant.
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.
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, ease of use, and configuration
options.
"AJAY R" <dba_pune@.hotmail.com> wrote in message
news:er$fIigRDHA.3132@.tk2msftngp13.phx.gbl...
> Hi
> Is there any diff. between Named Pipe& TCP-IP protocol from performance
> point of view there by I can force all the users connecting to server with
> TCP-IP proctocol only .
> Regards
> Ajay Rengunthwar
>
>

Developer Edition having issues connecting to server via TCP/IP

Don't know if there is a simple solution for this one or not. When
running SQL server on a machine with 2000 loaded and the complete SQL
package I don't have any issues. Now I'm trying to login using my XP
machine with MSSQL developer edition, and I can not connect to my
remote servers via TCP/IP. It can see the server, and it establishes a
connection, but I can't access my files, and the connection seems
incredibly slow. I have checked my firewall, and its fine. I'm just
wondering why my 2000 system can access it, but my XP can't. Any
ideas?Chris (chris.wisherd@.kenblanchard.com) writes:
> Don't know if there is a simple solution for this one or not. When
> running SQL server on a machine with 2000 loaded and the complete SQL
> package I don't have any issues. Now I'm trying to login using my XP
> machine with MSSQL developer edition, and I can not connect to my
> remote servers via TCP/IP. It can see the server, and it establishes a
> connection, but I can't access my files, and the connection seems
> incredibly slow. I have checked my firewall, and its fine. I'm just
> wondering why my 2000 system can access it, but my XP can't. Any
> ideas?

I'm confused, can't you connect at all, or is the communication just slow?

On which machine does the SQL Server you are connecting to run? Is the XP
machine in the same domain as the SQL Server machine?

What files are you unable to access? You usually don't use SQL Server
to access files.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Erland Sommarskog wrote:
> Chris (chris.wisherd@.kenblanchard.com) writes:
> > Don't know if there is a simple solution for this one or not. When
> > running SQL server on a machine with 2000 loaded and the complete SQL
> > package I don't have any issues. Now I'm trying to login using my XP
> > machine with MSSQL developer edition, and I can not connect to my
> > remote servers via TCP/IP. It can see the server, and it establishes a
> > connection, but I can't access my files, and the connection seems
> > incredibly slow. I have checked my firewall, and its fine. I'm just
> > wondering why my 2000 system can access it, but my XP can't. Any
> > ideas?
> I'm confused, can't you connect at all, or is the communication just slow?
> On which machine does the SQL Server you are connecting to run? Is the XP
> machine in the same domain as the SQL Server machine?
> What files are you unable to access? You usually don't use SQL Server
> to access files.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx

I can connect to the server, but it is slow. But I can't access
information such as the databases. It comes up with no items. I also
can't backup any of the data to a local machine. There wasn't any
issue until we loaded the 2003 Developer Edition on our XP machines.
I've loaded both service packs 3 and 4 hoping that would solve the
problem. I've checked TCP/IP setting, and the firewall.

The server I'm trying to access is a remote server running Windows
2000, with service pack 4, and it is in a different domain.|||Chris (chris.wisherd@.kenblanchard.com) writes:
> I can connect to the server, but it is slow. But I can't access
> information such as the databases. It comes up with no items. I also
> can't backup any of the data to a local machine. There wasn't any
> issue until we loaded the 2003 Developer Edition on our XP machines.
> I've loaded both service packs 3 and 4 hoping that would solve the
> problem. I've checked TCP/IP setting, and the firewall.
> The server I'm trying to access is a remote server running Windows
> 2000, with service pack 4, and it is in a different domain.

I realise that I should have asked what you are connecting with and
with which credentials.

From what you say, it sounds as it you connect with Enterprise Manager
with integrated security, but your Windows login has not been added to
BUILTIN\Administrators and on top of all databases are set to autoclose.
When databases are set to autoclose, and you connect as a non-priv user,
EM has to access every database to see if you are permitted, and this
can take forever.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx