July 16, 2004 at 10:05 am
The other day several users reported their sql apps were "not working". I found that several process were blocked by a single process (sp_who2). I spoke to the developers. They said that their new client install package used "Named Pipes", not "TCP/IP" to communicate between the client and the server. They think that that is the source of their blocking problem. (I don't)
Can a protocol cause this type of problem? Or is it just "bad" t-sql
Bill
July 17, 2004 at 8:07 pm
Using Named Pipes depending on the configuration can be slower, which would increase problems caused by blocking. Ultimately though, it's the bad code or design causing the blocking.
Derrick Leggett
Mean Old DBA
When life gives you a lemon, fire the DBA.
July 19, 2004 at 10:23 am
"Using Named Pipes depending on the configuration can be slower...."
Can anyone elaborate on the statement "depending on the configuration"? What types of configs can slow down named pipes?
TIA,
Bill
July 19, 2004 at 10:41 am
If you are using mixed mode authentication across a WAN with multiple domains on an undersized SQL server and/or unserized domain controller(s) and not a full up AD M$ network with more than one protocol on the network.
I've only had 2 named pipes connections work for me. And they were both at about 2:00 AM. Pick anyone of the above factors and ask why named pipes might not work? I think M$ just created named pipes to screw with us on the test.
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply