Re: Named Pipes vs TCP/IP
From: Howard Long (howard_at_howardlongxxx.com)
Date: 09/07/04
- Next message: Mailing Lists: "Re: BACKUP LOG <database name> WITH TRUNCATE_ONLY failing"
- Previous message: Adam Machanic: "Re: BACKUP LOG <database name> WITH TRUNCATE_ONLY failing"
- In reply to: Bob Castleman: "Named Pipes vs TCP/IP"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 7 Sep 2004 15:37:24 +0000 (UTC)
"Bob Castleman" <nomail@here> wrote in message
news:OAh7NLOlEHA.324@TK2MSFTNGP11.phx.gbl...
> Why would one choose Named Pipes over TCP/IP for the client net lib? We
have
> noticed for some of our customers that changing to named pipes speeds up
the
> response times of our application. But it is my understanding that a
> properly configured LAN should work fine with TCP/IP.
Don't know if this is your problem, but there was a bug a while ago in SQL
Server 2000 to do with the introduction of Kerberos aware authentication
using DBLibrary connections over TCP/IP.
IIRC, the SQL Client and SQL Server would not correctly negotiate packet
sizes. This could be circumvented by explicitly overriding the default
packet size in the client app. This was resolved in SQL Server SP2.
Kind Regards, Howard
- Next message: Mailing Lists: "Re: BACKUP LOG <database name> WITH TRUNCATE_ONLY failing"
- Previous message: Adam Machanic: "Re: BACKUP LOG <database name> WITH TRUNCATE_ONLY failing"
- In reply to: Bob Castleman: "Named Pipes vs TCP/IP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
