accessing sql server via IP is very slow

Hello,
we got a situation with sql 2005 server that configured to be access with
both name pipes and tcp/ip.
while accessing the server via name pipes is very fast other method ip is
very slow
someone could put a light on this issue
ThanksCan you give some information about your network config?
"Tal Bar-Or" <TalBarOr@.discussions.microsoft.com> wrote in message
news:4584EDEB-61AA-4439-9A5D-D03CBAE4BD33@.microsoft.com...
> Hello,
> we got a situation with sql 2005 server that configured to be access with
> both name pipes and tcp/ip.
> while accessing the server via name pipes is very fast other method ip is
> very slow
> someone could put a light on this issue
> Thanks|||we have standard active directory with dns and wins all connected to switch
with one vlan without any restriction.
"Aaron Bertrand [SQL Server MVP]" wrote:
> Can you give some information about your network config?
>
> "Tal Bar-Or" <TalBarOr@.discussions.microsoft.com> wrote in message
> news:4584EDEB-61AA-4439-9A5D-D03CBAE4BD33@.microsoft.com...
> > Hello,
> >
> > we got a situation with sql 2005 server that configured to be access with
> > both name pipes and tcp/ip.
> > while accessing the server via name pipes is very fast other method ip is
> > very slow
> > someone could put a light on this issue
> > Thanks
>
>|||Have you talked to your network administrator? This could be how the LAN is
configured (e.g. it could be that IPs are routed differently...)
"Tal Bar-Or" <TalBarOr@.discussions.microsoft.com> wrote in message
news:45F5967B-B303-4E44-9F63-8096A9C22006@.microsoft.com...
> we have standard active directory with dns and wins all connected to
> switch
> with one vlan without any restriction.
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> Can you give some information about your network config?
>>
>> "Tal Bar-Or" <TalBarOr@.discussions.microsoft.com> wrote in message
>> news:4584EDEB-61AA-4439-9A5D-D03CBAE4BD33@.microsoft.com...
>> > Hello,
>> >
>> > we got a situation with sql 2005 server that configured to be access
>> > with
>> > both name pipes and tcp/ip.
>> > while accessing the server via name pipes is very fast other method ip
>> > is
>> > very slow
>> > someone could put a light on this issue
>> > Thanks
>>|||Also, is it just SQL traffic? What do ping, tracert, file copy etc. look
like using both connection methods?
And if IP is slow, then why not just use named pipes? I gather that you
want to understand the problem, but personally I would rather spend my time
on software performance issues and leave the hardware stuff to the hardware
folks. :-)|||This is definitely a question for your network admin to address.
You could try using the tracert dos command to see if there is a single
point in the path that is causing the majority of the slowdown.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Tal Bar-Or" <TalBarOr@.discussions.microsoft.com> wrote in message
news:4584EDEB-61AA-4439-9A5D-D03CBAE4BD33@.microsoft.com...
> Hello,
> we got a situation with sql 2005 server that configured to be access with
> both name pipes and tcp/ip.
> while accessing the server via name pipes is very fast other method ip is
> very slow
> someone could put a light on this issue
> Thanks|||Thanks for the answer
could you please point me to an article how difference made by connecting
via name pipes and tcp/ip
thanks
"Aaron Bertrand [SQL Server MVP]" wrote:
> Also, is it just SQL traffic? What do ping, tracert, file copy etc. look
> like using both connection methods?
> And if IP is slow, then why not just use named pipes? I gather that you
> want to understand the problem, but personally I would rather spend my time
> on software performance issues and leave the hardware stuff to the hardware
> folks. :-)
>
>|||Just to be clear, the clients in question are not on the same server?
Quoting the Books On Line:
"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 that is running an instance of SQL Server, the local Named
Pipes protocol is an option. Local named pipes runs in kernel mode and
is very fast."
Roy Harvey
Beacon Falls, CT
On Mon, 28 Apr 2008 04:59:01 -0700, Tal Bar-Or
<TalBarOr@.discussions.microsoft.com> wrote:
>Hello,
>we got a situation with sql 2005 server that configured to be access with
>both name pipes and tcp/ip.
>while accessing the server via name pipes is very fast other method ip is
>very slow
>someone could put a light on this issue
>Thanks|||> could you please point me to an article how difference made by connecting
> via name pipes and tcp/ip
I don't know of one specifically off-hand. Did you try Google?