Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
enable in network libraries. I noticed in EM under current activity and
process info for some processes named pipes is used and for other processes
something called LPC is used. Is LPC aka TCP/IP? It looks like when the
"host" for the process is the server, then it uses LPC but when the "host" i
s
a workstation it uses named pipes. Does it use named pipes for the
workstations because it is listed first in the network libraries? Is named
pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
second or just remove named pipes?
Thanks,
--
Dan D.Hi Dan
"Dan D." wrote:
> Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> enable in network libraries. I noticed in EM under current activity and
> process info for some processes named pipes is used and for other processe
s
> something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> "host" for the process is the server, then it uses LPC but when the "host"
is
> a workstation it uses named pipes. Does it use named pipes for the
> workstations because it is listed first in the network libraries? Is named
> pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> second or just remove named pipes?
> Thanks,
> --
> Dan D.
LPC is a shared memory connection, that is why the host is the server
itself. The protocol used will be order by they are listed on the client, if
you client had TCP as the first protocol to use and the server has TCP/IP
enabled then that would be used. TCP/IP was made the primary protocol in SP3
a
so you may want to check what versions you are using. To see the client
protocols installed use the Client Networking Utility (on the client) there
are buttons that will let you change the order, and to check the for server
protocols use the Server Networking Utility on the server.
As far as speed, I believe they can be about the same, but with names pipes
there are potential security issues as you are connecting directly through
the filesystem of the server.
As far as removing named pipes, it is your choice.
John|||I understand. Thanks.
--
Dan D.
"John Bell" wrote:
> Hi Dan
> "Dan D." wrote:
>
> LPC is a shared memory connection, that is why the host is the server
> itself. The protocol used will be order by they are listed on the client,
if
> you client had TCP as the first protocol to use and the server has TCP/IP
> enabled then that would be used. TCP/IP was made the primary protocol in S
P3a
> so you may want to check what versions you are using. To see the client
> protocols installed use the Client Networking Utility (on the client) ther
e
> are buttons that will let you change the order, and to check the for serve
r
> protocols use the Server Networking Utility on the server.
> As far as speed, I believe they can be about the same, but with names pipe
s
> there are potential security issues as you are connecting directly through
> the filesystem of the server.
> As far as removing named pipes, it is your choice.
> John|||"Dan D." wrote:
> I understand. Thanks.
> --
> Dan D.
That is one of us then! I didn't realise it read so badly!
John
Friday, March 30, 2012
Named Pipes vs TCP
How would one go about adjusting the default connection to the SQL Server on the client side, using either Named Pipes or TCP as the default?Look for the Client Network Utility tool in the SQL Server program group. Or start->run CliConfig.exe.|||any way to pull of the defaulting programmatically??|||Yes, but the mechanics vary a lot depending on how you are programming. The easiest/surest way is to use the NETWORK parameter within DSN-Less connection strings (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnodbc/html/odbcsql.asp).
-PatP|||Looks like the ticket, thanks for your assistance...
-PatP|||Looks like the ticket, thanks for your assistance...
named pipes vs tcp
Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
enable in network libraries. I noticed in EM under current activity and
process info for some processes named pipes is used and for other processes
something called LPC is used. Is LPC aka TCP/IP? It looks like when the
"host" for the process is the server, then it uses LPC but when the "host" is
a workstation it uses named pipes. Does it use named pipes for the
workstations because it is listed first in the network libraries? Is named
pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
second or just remove named pipes?
Thanks,
Dan D.
Hi Dan
"Dan D." wrote:
> Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> enable in network libraries. I noticed in EM under current activity and
> process info for some processes named pipes is used and for other processes
> something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> "host" for the process is the server, then it uses LPC but when the "host" is
> a workstation it uses named pipes. Does it use named pipes for the
> workstations because it is listed first in the network libraries? Is named
> pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> second or just remove named pipes?
> Thanks,
> --
> Dan D.
LPC is a shared memory connection, that is why the host is the server
itself. The protocol used will be order by they are listed on the client, if
you client had TCP as the first protocol to use and the server has TCP/IP
enabled then that would be used. TCP/IP was made the primary protocol in SP3a
so you may want to check what versions you are using. To see the client
protocols installed use the Client Networking Utility (on the client) there
are buttons that will let you change the order, and to check the for server
protocols use the Server Networking Utility on the server.
As far as speed, I believe they can be about the same, but with names pipes
there are potential security issues as you are connecting directly through
the filesystem of the server.
As far as removing named pipes, it is your choice.
John
|||I understand. Thanks.
Dan D.
"John Bell" wrote:
> Hi Dan
> "Dan D." wrote:
>
> LPC is a shared memory connection, that is why the host is the server
> itself. The protocol used will be order by they are listed on the client, if
> you client had TCP as the first protocol to use and the server has TCP/IP
> enabled then that would be used. TCP/IP was made the primary protocol in SP3a
> so you may want to check what versions you are using. To see the client
> protocols installed use the Client Networking Utility (on the client) there
> are buttons that will let you change the order, and to check the for server
> protocols use the Server Networking Utility on the server.
> As far as speed, I believe they can be about the same, but with names pipes
> there are potential security issues as you are connecting directly through
> the filesystem of the server.
> As far as removing named pipes, it is your choice.
> John
|||"Dan D." wrote:
> I understand. Thanks.
> --
> Dan D.
That is one of us then! I didn't realise it read so badly!
John
enable in network libraries. I noticed in EM under current activity and
process info for some processes named pipes is used and for other processes
something called LPC is used. Is LPC aka TCP/IP? It looks like when the
"host" for the process is the server, then it uses LPC but when the "host" is
a workstation it uses named pipes. Does it use named pipes for the
workstations because it is listed first in the network libraries? Is named
pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
second or just remove named pipes?
Thanks,
Dan D.
Hi Dan
"Dan D." wrote:
> Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> enable in network libraries. I noticed in EM under current activity and
> process info for some processes named pipes is used and for other processes
> something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> "host" for the process is the server, then it uses LPC but when the "host" is
> a workstation it uses named pipes. Does it use named pipes for the
> workstations because it is listed first in the network libraries? Is named
> pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> second or just remove named pipes?
> Thanks,
> --
> Dan D.
LPC is a shared memory connection, that is why the host is the server
itself. The protocol used will be order by they are listed on the client, if
you client had TCP as the first protocol to use and the server has TCP/IP
enabled then that would be used. TCP/IP was made the primary protocol in SP3a
so you may want to check what versions you are using. To see the client
protocols installed use the Client Networking Utility (on the client) there
are buttons that will let you change the order, and to check the for server
protocols use the Server Networking Utility on the server.
As far as speed, I believe they can be about the same, but with names pipes
there are potential security issues as you are connecting directly through
the filesystem of the server.
As far as removing named pipes, it is your choice.
John
|||I understand. Thanks.
Dan D.
"John Bell" wrote:
> Hi Dan
> "Dan D." wrote:
>
> LPC is a shared memory connection, that is why the host is the server
> itself. The protocol used will be order by they are listed on the client, if
> you client had TCP as the first protocol to use and the server has TCP/IP
> enabled then that would be used. TCP/IP was made the primary protocol in SP3a
> so you may want to check what versions you are using. To see the client
> protocols installed use the Client Networking Utility (on the client) there
> are buttons that will let you change the order, and to check the for server
> protocols use the Server Networking Utility on the server.
> As far as speed, I believe they can be about the same, but with names pipes
> there are potential security issues as you are connecting directly through
> the filesystem of the server.
> As far as removing named pipes, it is your choice.
> John
|||"Dan D." wrote:
> I understand. Thanks.
> --
> Dan D.
That is one of us then! I didn't realise it read so badly!
John
named pipes vs tcp
Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
enable in network libraries. I noticed in EM under current activity and
process info for some processes named pipes is used and for other processes
something called LPC is used. Is LPC aka TCP/IP? It looks like when the
"host" for the process is the server, then it uses LPC but when the "host" is
a workstation it uses named pipes. Does it use named pipes for the
workstations because it is listed first in the network libraries? Is named
pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
second or just remove named pipes?
Thanks,
--
Dan D.Hi Dan
"Dan D." wrote:
> Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> enable in network libraries. I noticed in EM under current activity and
> process info for some processes named pipes is used and for other processes
> something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> "host" for the process is the server, then it uses LPC but when the "host" is
> a workstation it uses named pipes. Does it use named pipes for the
> workstations because it is listed first in the network libraries? Is named
> pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> second or just remove named pipes?
> Thanks,
> --
> Dan D.
LPC is a shared memory connection, that is why the host is the server
itself. The protocol used will be order by they are listed on the client, if
you client had TCP as the first protocol to use and the server has TCP/IP
enabled then that would be used. TCP/IP was made the primary protocol in SP3a
so you may want to check what versions you are using. To see the client
protocols installed use the Client Networking Utility (on the client) there
are buttons that will let you change the order, and to check the for server
protocols use the Server Networking Utility on the server.
As far as speed, I believe they can be about the same, but with names pipes
there are potential security issues as you are connecting directly through
the filesystem of the server.
As far as removing named pipes, it is your choice.
John|||I understand. Thanks.
--
Dan D.
"John Bell" wrote:
> Hi Dan
> "Dan D." wrote:
> > Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> > enable in network libraries. I noticed in EM under current activity and
> > process info for some processes named pipes is used and for other processes
> > something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> > "host" for the process is the server, then it uses LPC but when the "host" is
> > a workstation it uses named pipes. Does it use named pipes for the
> > workstations because it is listed first in the network libraries? Is named
> > pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> > second or just remove named pipes?
> >
> > Thanks,
> > --
> > Dan D.
> LPC is a shared memory connection, that is why the host is the server
> itself. The protocol used will be order by they are listed on the client, if
> you client had TCP as the first protocol to use and the server has TCP/IP
> enabled then that would be used. TCP/IP was made the primary protocol in SP3a
> so you may want to check what versions you are using. To see the client
> protocols installed use the Client Networking Utility (on the client) there
> are buttons that will let you change the order, and to check the for server
> protocols use the Server Networking Utility on the server.
> As far as speed, I believe they can be about the same, but with names pipes
> there are potential security issues as you are connecting directly through
> the filesystem of the server.
> As far as removing named pipes, it is your choice.
> John|||"Dan D." wrote:
> I understand. Thanks.
> --
> Dan D.
That is one of us then! I didn't realise it read so badly!
Johnsql
enable in network libraries. I noticed in EM under current activity and
process info for some processes named pipes is used and for other processes
something called LPC is used. Is LPC aka TCP/IP? It looks like when the
"host" for the process is the server, then it uses LPC but when the "host" is
a workstation it uses named pipes. Does it use named pipes for the
workstations because it is listed first in the network libraries? Is named
pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
second or just remove named pipes?
Thanks,
--
Dan D.Hi Dan
"Dan D." wrote:
> Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> enable in network libraries. I noticed in EM under current activity and
> process info for some processes named pipes is used and for other processes
> something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> "host" for the process is the server, then it uses LPC but when the "host" is
> a workstation it uses named pipes. Does it use named pipes for the
> workstations because it is listed first in the network libraries? Is named
> pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> second or just remove named pipes?
> Thanks,
> --
> Dan D.
LPC is a shared memory connection, that is why the host is the server
itself. The protocol used will be order by they are listed on the client, if
you client had TCP as the first protocol to use and the server has TCP/IP
enabled then that would be used. TCP/IP was made the primary protocol in SP3a
so you may want to check what versions you are using. To see the client
protocols installed use the Client Networking Utility (on the client) there
are buttons that will let you change the order, and to check the for server
protocols use the Server Networking Utility on the server.
As far as speed, I believe they can be about the same, but with names pipes
there are potential security issues as you are connecting directly through
the filesystem of the server.
As far as removing named pipes, it is your choice.
John|||I understand. Thanks.
--
Dan D.
"John Bell" wrote:
> Hi Dan
> "Dan D." wrote:
> > Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> > enable in network libraries. I noticed in EM under current activity and
> > process info for some processes named pipes is used and for other processes
> > something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> > "host" for the process is the server, then it uses LPC but when the "host" is
> > a workstation it uses named pipes. Does it use named pipes for the
> > workstations because it is listed first in the network libraries? Is named
> > pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> > second or just remove named pipes?
> >
> > Thanks,
> > --
> > Dan D.
> LPC is a shared memory connection, that is why the host is the server
> itself. The protocol used will be order by they are listed on the client, if
> you client had TCP as the first protocol to use and the server has TCP/IP
> enabled then that would be used. TCP/IP was made the primary protocol in SP3a
> so you may want to check what versions you are using. To see the client
> protocols installed use the Client Networking Utility (on the client) there
> are buttons that will let you change the order, and to check the for server
> protocols use the Server Networking Utility on the server.
> As far as speed, I believe they can be about the same, but with names pipes
> there are potential security issues as you are connecting directly through
> the filesystem of the server.
> As far as removing named pipes, it is your choice.
> John|||"Dan D." wrote:
> I understand. Thanks.
> --
> Dan D.
That is one of us then! I didn't realise it read so badly!
Johnsql
named pipes versus tcpip
Is using the named pipes protocol more/less secure and/or
slower than using tcpip to connect to SQL server?
"Colleen Rossman" <anonymous@.discussions.microsoft.com> wrote in message
news:136401c4aba9$c7ef54b0$a601280a@.phx.gbl...
> Is using the named pipes protocol more/less secure and/or
> slower than using tcpip to connect to SQL server?
Named Pipes is equally secure (ie, vulerable to ethernet sniffing).
In two special cases Named Pipes is faster: on the same machine, and over
local-area networks using the NetBUI protocol. In other cases TCP/IP is
faster, since in those cases Named Pipes would be running _over_ TCP/IP.
Remember that all the client netlibs date from before TCP/IP took over the
world. Back then you would choose the netlib which matched your LAN's
network protocol. Well today every network runs on IP, so everyone uses the
TCP/IP netlib.
David
slower than using tcpip to connect to SQL server?
"Colleen Rossman" <anonymous@.discussions.microsoft.com> wrote in message
news:136401c4aba9$c7ef54b0$a601280a@.phx.gbl...
> Is using the named pipes protocol more/less secure and/or
> slower than using tcpip to connect to SQL server?
Named Pipes is equally secure (ie, vulerable to ethernet sniffing).
In two special cases Named Pipes is faster: on the same machine, and over
local-area networks using the NetBUI protocol. In other cases TCP/IP is
faster, since in those cases Named Pipes would be running _over_ TCP/IP.
Remember that all the client netlibs date from before TCP/IP took over the
world. Back then you would choose the netlib which matched your LAN's
network protocol. Well today every network runs on IP, so everyone uses the
TCP/IP netlib.
David
named pipes under alias
I have a SQLSERVER INSTANCE A, to which I want to connect from a Client as TEST, using the SQL Server alias functionality under the client network utility program. The alias is working fine with the TCP\IP connection but it fails when I try to connect to the SQL Server using the named pipes. In my case I'm trying to connect to a named instance of SQL Server 2000 using the following pipe: \\servername\pipe\mssql$instancename\sql\query
Any help?I have just tried this. Pain in the neck, too. When you change the name of the alias, the client network utility is all helpful, and changes the actual path, and server name. So you have to get the right path, and save it of in notepad or something. Change the name of the alias, replace the name of the server with the name of the server you want, then recover the path from notepad. I tried it, and it did not work. Then I hit the Apply button. Now it works. Does that approximate what you went through?|||I can connect to any server using the alias name with the TCP/IP, but the same doesn't work with the Named Pipes.
Any help?I have just tried this. Pain in the neck, too. When you change the name of the alias, the client network utility is all helpful, and changes the actual path, and server name. So you have to get the right path, and save it of in notepad or something. Change the name of the alias, replace the name of the server with the name of the server you want, then recover the path from notepad. I tried it, and it did not work. Then I hit the Apply button. Now it works. Does that approximate what you went through?|||I can connect to any server using the alias name with the TCP/IP, but the same doesn't work with the Named Pipes.
Named pipes question.
Is it possible to configure named pipes only on one NIC and tcpip on the
other' (SQL 2000 sp3)
PierreNot in SQL 2000. You cannot protocol 'affinitize' NIC's
(Hopefully in the next version)
"Pierre" <Pierre.roman@.qunara.com.nospam> wrote in message
news:%23E0dhpvqDHA.2632@.TK2MSFTNGP09.phx.gbl...
> Is it possible to configure named pipes only on one NIC and tcpip on the
> other' (SQL 2000 sp3)
> Pierre
>|||Thanks
"Dieter Katzenland" <deiter@.rrtc.com> wrote in message
news:uYNs2SwqDHA.2772@.TK2MSFTNGP12.phx.gbl...
> Not in SQL 2000. You cannot protocol 'affinitize' NIC's
> (Hopefully in the next version)
> "Pierre" <Pierre.roman@.qunara.com.nospam> wrote in message
> news:%23E0dhpvqDHA.2632@.TK2MSFTNGP09.phx.gbl...
> > Is it possible to configure named pipes only on one NIC and tcpip on the
> > other' (SQL 2000 sp3)
> >
> > Pierre
> >
> >
>|||Pierre,
Yes, but only with a (software) firewall.
Named pipes use SMB, TCP/IP uses port 1433 (default).
You cannot currently separate the protocols by any binding or SQL setup that I know of.
Regards
AJ
"Pierre" <Pierre.roman@.qunara.com.nospam> wrote in message news:%23E0dhpvqDHA.2632@.TK2MSFTNGP09.phx.gbl...
> Is it possible to configure named pipes only on one NIC and tcpip on the
> other' (SQL 2000 sp3)
> Pierre
>
other' (SQL 2000 sp3)
PierreNot in SQL 2000. You cannot protocol 'affinitize' NIC's
(Hopefully in the next version)
"Pierre" <Pierre.roman@.qunara.com.nospam> wrote in message
news:%23E0dhpvqDHA.2632@.TK2MSFTNGP09.phx.gbl...
> Is it possible to configure named pipes only on one NIC and tcpip on the
> other' (SQL 2000 sp3)
> Pierre
>|||Thanks
"Dieter Katzenland" <deiter@.rrtc.com> wrote in message
news:uYNs2SwqDHA.2772@.TK2MSFTNGP12.phx.gbl...
> Not in SQL 2000. You cannot protocol 'affinitize' NIC's
> (Hopefully in the next version)
> "Pierre" <Pierre.roman@.qunara.com.nospam> wrote in message
> news:%23E0dhpvqDHA.2632@.TK2MSFTNGP09.phx.gbl...
> > Is it possible to configure named pipes only on one NIC and tcpip on the
> > other' (SQL 2000 sp3)
> >
> > Pierre
> >
> >
>|||Pierre,
Yes, but only with a (software) firewall.
Named pipes use SMB, TCP/IP uses port 1433 (default).
You cannot currently separate the protocols by any binding or SQL setup that I know of.
Regards
AJ
"Pierre" <Pierre.roman@.qunara.com.nospam> wrote in message news:%23E0dhpvqDHA.2632@.TK2MSFTNGP09.phx.gbl...
> Is it possible to configure named pipes only on one NIC and tcpip on the
> other' (SQL 2000 sp3)
> Pierre
>
Subscribe to:
Posts (Atom)