Hello
Which is the difference between using named pipes and TCP/IP?
Is it possible to enable TCP/IP and disable named pipes at the same time for
the server communication?
What happens if I disable named pipes?
Tanx
Alejandra Parra
Mexico
Named Pipes is MUCH slower, unless it is between servers, where it runs in
the kernal. I believe it has to do with the ability to queue requests - but
I'm not sure about that.
I usually disable named pipes on my servers. Otherwise people create DSNs
to connect and indicate Named Pipes, then wonder why the application is so
slow.
"Alejandra Parra" wrote:
> Hello
> Which is the difference between using named pipes and TCP/IP?
> Is it possible to enable TCP/IP and disable named pipes at the same time for
> the server communication?
> What happens if I disable named pipes?
> Tanx
> Alejandra Parra
> Mexico
>
>
|||"Alejandra Parra" <alparrita@.hotmail.com> wrote in message
news:OzuMkbRkEHA.2908@.tk2msftngp13.phx.gbl...
> Which is the difference between using named pipes and TCP/IP?
SQL Server BOL has a good write-up on the differences between these two
libraries see 'Named Pipes vs. TCP/IP Sockets'.
> Is it possible to enable TCP/IP and disable named pipes at the same time
for
> the server communication?
Yes, just make sure the network libraries are set up the same way on the
client side.
> What happens if I disable named pipes?
Most likely nothing... I've seen some old utilities and software dependent
on named pipes, however it's unlikely to effect you. As always, test before
deploying to production.
Steve
Showing posts with label enable. Show all posts
Showing posts with label enable. Show all posts
Friday, March 30, 2012
named pipes?
Hello
Which is the difference between using named pipes and TCP/IP?
Is it possible to enable TCP/IP and disable named pipes at the same time for
the server communication?
What happens if I disable named pipes?
Tanx
Alejandra Parra
MexicoNamed Pipes is MUCH slower, unless it is between servers, where it runs in
the kernal. I believe it has to do with the ability to queue requests - but
I'm not sure about that.
I usually disable named pipes on my servers. Otherwise people create DSNs
to connect and indicate Named Pipes, then wonder why the application is so
slow.
"Alejandra Parra" wrote:
> Hello
> Which is the difference between using named pipes and TCP/IP?
> Is it possible to enable TCP/IP and disable named pipes at the same time f
or
> the server communication?
> What happens if I disable named pipes?
> Tanx
> Alejandra Parra
> Mexico
>
>|||"Alejandra Parra" <alparrita@.hotmail.com> wrote in message
news:OzuMkbRkEHA.2908@.tk2msftngp13.phx.gbl...
> Which is the difference between using named pipes and TCP/IP?
SQL Server BOL has a good write-up on the differences between these two
libraries see 'Named Pipes vs. TCP/IP Sockets'.
> Is it possible to enable TCP/IP and disable named pipes at the same time
for
> the server communication?
Yes, just make sure the network libraries are set up the same way on the
client side.
> What happens if I disable named pipes?
Most likely nothing... I've seen some old utilities and software dependent
on named pipes, however it's unlikely to effect you. As always, test before
deploying to production.
Steve
Which is the difference between using named pipes and TCP/IP?
Is it possible to enable TCP/IP and disable named pipes at the same time for
the server communication?
What happens if I disable named pipes?
Tanx
Alejandra Parra
MexicoNamed Pipes is MUCH slower, unless it is between servers, where it runs in
the kernal. I believe it has to do with the ability to queue requests - but
I'm not sure about that.
I usually disable named pipes on my servers. Otherwise people create DSNs
to connect and indicate Named Pipes, then wonder why the application is so
slow.
"Alejandra Parra" wrote:
> Hello
> Which is the difference between using named pipes and TCP/IP?
> Is it possible to enable TCP/IP and disable named pipes at the same time f
or
> the server communication?
> What happens if I disable named pipes?
> Tanx
> Alejandra Parra
> Mexico
>
>|||"Alejandra Parra" <alparrita@.hotmail.com> wrote in message
news:OzuMkbRkEHA.2908@.tk2msftngp13.phx.gbl...
> Which is the difference between using named pipes and TCP/IP?
SQL Server BOL has a good write-up on the differences between these two
libraries see 'Named Pipes vs. TCP/IP Sockets'.
> Is it possible to enable TCP/IP and disable named pipes at the same time
for
> the server communication?
Yes, just make sure the network libraries are set up the same way on the
client side.
> What happens if I disable named pipes?
Most likely nothing... I've seen some old utilities and software dependent
on named pipes, however it's unlikely to effect you. As always, test before
deploying to production.
Steve
named pipes?
Hello
Which is the difference between using named pipes and TCP/IP?
Is it possible to enable TCP/IP and disable named pipes at the same time for
the server communication?
What happens if I disable named pipes?
Tanx
Alejandra Parra
Mexico"Alejandra Parra" <alparrita@.hotmail.com> wrote in message
news:OzuMkbRkEHA.2908@.tk2msftngp13.phx.gbl...
> Which is the difference between using named pipes and TCP/IP?
SQL Server BOL has a good write-up on the differences between these two
libraries see 'Named Pipes vs. TCP/IP Sockets'.
> Is it possible to enable TCP/IP and disable named pipes at the same time
for
> the server communication?
Yes, just make sure the network libraries are set up the same way on the
client side.
> What happens if I disable named pipes?
Most likely nothing... I've seen some old utilities and software dependent
on named pipes, however it's unlikely to effect you. As always, test before
deploying to production.
Steve
Which is the difference between using named pipes and TCP/IP?
Is it possible to enable TCP/IP and disable named pipes at the same time for
the server communication?
What happens if I disable named pipes?
Tanx
Alejandra Parra
Mexico"Alejandra Parra" <alparrita@.hotmail.com> wrote in message
news:OzuMkbRkEHA.2908@.tk2msftngp13.phx.gbl...
> Which is the difference between using named pipes and TCP/IP?
SQL Server BOL has a good write-up on the differences between these two
libraries see 'Named Pipes vs. TCP/IP Sockets'.
> Is it possible to enable TCP/IP and disable named pipes at the same time
for
> the server communication?
Yes, just make sure the network libraries are set up the same way on the
client side.
> What happens if I disable named pipes?
Most likely nothing... I've seen some old utilities and software dependent
on named pipes, however it's unlikely to effect you. As always, test before
deploying to production.
Steve
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
Monday, March 26, 2012
named instances and sp3a - how to enable access?
As I understand it, the slammer virus took advantage of port 1434 which is e
nabled over udp for sql clients to find out the ports named instances are us
ing. If applying sp3a disables listening on port 1434, can named instances s
till be used? Do the ports
need to be known and hardcoded in advance?
TIA,
John BrownIn the Server network Utiliy simply choose a fixed port number, and the
clients would have to know the fixed port number to connect.
Or you could still use Dynamic ports, (the check box) and enable port 1434,
and the end user does NOT have to know the port number...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"John Brown" <anonymous@.discussions.microsoft.com> wrote in message
news:F9DBE64E-3137-41B3-91D1-ECDFC0086B08@.microsoft.com...
> As I understand it, the slammer virus took advantage of port 1434 which is
enabled over udp for sql clients to find out the ports named instances are
using. If applying sp3a disables listening on port 1434, can named instances
still be used? Do the ports need to be known and hardcoded in advance?
> TIA,
> John Brown|||Thanks Wayne,
so if I enable 1434, does this open me up to the slammer virus still?
TIA,
John Brown|||SP3a fixes the exploit in the SQL Server Resolution Service used by Slammer,
it does not stop the server listening on UDP1434 as this is required for
resolving endpoints for named instances unless every client has the port
hard coded into a connection string or an alias in the client network
utlity. As long as you have SP3a applied you'll be okay but make sure that
port is still blocked on external firewalls.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"John Brown" <anonymous@.discussions.microsoft.com> wrote in message
news:F5708C23-286E-49B6-88BC-4CD6C5F1C768@.microsoft.com...
> Thanks Wayne,
> so if I enable 1434, does this open me up to the slammer virus still?
> TIA,
> John Brown
nabled over udp for sql clients to find out the ports named instances are us
ing. If applying sp3a disables listening on port 1434, can named instances s
till be used? Do the ports
need to be known and hardcoded in advance?
TIA,
John BrownIn the Server network Utiliy simply choose a fixed port number, and the
clients would have to know the fixed port number to connect.
Or you could still use Dynamic ports, (the check box) and enable port 1434,
and the end user does NOT have to know the port number...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"John Brown" <anonymous@.discussions.microsoft.com> wrote in message
news:F9DBE64E-3137-41B3-91D1-ECDFC0086B08@.microsoft.com...
> As I understand it, the slammer virus took advantage of port 1434 which is
enabled over udp for sql clients to find out the ports named instances are
using. If applying sp3a disables listening on port 1434, can named instances
still be used? Do the ports need to be known and hardcoded in advance?
> TIA,
> John Brown|||Thanks Wayne,
so if I enable 1434, does this open me up to the slammer virus still?
TIA,
John Brown|||SP3a fixes the exploit in the SQL Server Resolution Service used by Slammer,
it does not stop the server listening on UDP1434 as this is required for
resolving endpoints for named instances unless every client has the port
hard coded into a connection string or an alias in the client network
utlity. As long as you have SP3a applied you'll be okay but make sure that
port is still blocked on external firewalls.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"John Brown" <anonymous@.discussions.microsoft.com> wrote in message
news:F5708C23-286E-49B6-88BC-4CD6C5F1C768@.microsoft.com...
> Thanks Wayne,
> so if I enable 1434, does this open me up to the slammer virus still?
> TIA,
> John Brown
named instances and sp3a - how to enable access?
As I understand it, the slammer virus took advantage of port 1434 which is enabled over udp for sql clients to find out the ports named instances are using. If applying sp3a disables listening on port 1434, can named instances still be used? Do the ports need to be known and hardcoded in advance
TIA
John BrownIn the Server network Utiliy simply choose a fixed port number, and the
clients would have to know the fixed port number to connect.
Or you could still use Dynamic ports, (the check box) and enable port 1434,
and the end user does NOT have to know the port number...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"John Brown" <anonymous@.discussions.microsoft.com> wrote in message
news:F9DBE64E-3137-41B3-91D1-ECDFC0086B08@.microsoft.com...
> As I understand it, the slammer virus took advantage of port 1434 which is
enabled over udp for sql clients to find out the ports named instances are
using. If applying sp3a disables listening on port 1434, can named instances
still be used? Do the ports need to be known and hardcoded in advance?
> TIA,
> John Brown|||SP3a fixes the exploit in the SQL Server Resolution Service used by Slammer,
it does not stop the server listening on UDP1434 as this is required for
resolving endpoints for named instances unless every client has the port
hard coded into a connection string or an alias in the client network
utlity. As long as you have SP3a applied you'll be okay but make sure that
port is still blocked on external firewalls.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"John Brown" <anonymous@.discussions.microsoft.com> wrote in message
news:F5708C23-286E-49B6-88BC-4CD6C5F1C768@.microsoft.com...
> Thanks Wayne,
> so if I enable 1434, does this open me up to the slammer virus still?
> TIA,
> John Brown
TIA
John BrownIn the Server network Utiliy simply choose a fixed port number, and the
clients would have to know the fixed port number to connect.
Or you could still use Dynamic ports, (the check box) and enable port 1434,
and the end user does NOT have to know the port number...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"John Brown" <anonymous@.discussions.microsoft.com> wrote in message
news:F9DBE64E-3137-41B3-91D1-ECDFC0086B08@.microsoft.com...
> As I understand it, the slammer virus took advantage of port 1434 which is
enabled over udp for sql clients to find out the ports named instances are
using. If applying sp3a disables listening on port 1434, can named instances
still be used? Do the ports need to be known and hardcoded in advance?
> TIA,
> John Brown|||SP3a fixes the exploit in the SQL Server Resolution Service used by Slammer,
it does not stop the server listening on UDP1434 as this is required for
resolving endpoints for named instances unless every client has the port
hard coded into a connection string or an alias in the client network
utlity. As long as you have SP3a applied you'll be okay but make sure that
port is still blocked on external firewalls.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"John Brown" <anonymous@.discussions.microsoft.com> wrote in message
news:F5708C23-286E-49B6-88BC-4CD6C5F1C768@.microsoft.com...
> Thanks Wayne,
> so if I enable 1434, does this open me up to the slammer virus still?
> TIA,
> John Brown
Friday, March 23, 2012
name of table used for logging in sql server
Hello,
When I enable logging where is the table name specified for SQL Server?
Can I specify the table name?
Thanks,
Michael
No. The SQL Server log provider, which writes log entries to the sysdtslog90 table in a SQL Server 2005 database.
Subscribe to:
Posts (Atom)