I do not beleive it is a DB as in database problem. It could be a sql
server issue. The curious thing is that BOTH transport mechanisms have to
go over the network, so if there is a general network overutilization issue
that is causing the dropouts, it should happen to both types of connections.
What is the error(s) you get when the connections are dropping out? Are
they timeout related? If so, THAT could be a database design/code problem
whereby queries are running so slowly they are timing out. If you use Query
Analyzer from desktops and connect (specifying both named pipes and tcp/ip
via aliases), do you get dropouts?
Microsoft has a free network monitoring/capture tool called Network Monitor
3.0. There are other freebies that can be found on the net (try
sourceforge.net).
Good luck. Intermittent problems are the toughest to solve!
--
TheSQLGuru
President
Indicium Resources, Inc.
[quoted text, click to view] "Andre Gibson" <AndreGibson@discussions.microsoft.com> wrote in message
news:DEC99D3A-0301-49BF-84AA-A68C0BB11FC0@microsoft.com...
> Hello all,
> My company is running an application that uses sql server 2000 sp3. Sql
> server 2000 is configured to accept only TCP/IP (port 1433) or Named
> Pipes.
> We prefer to use TCP/IP but we are having issues with users losing there
> connection to the DB if they use TCP/IP. The problem is sporadic, and I am
> tring to find a definitive way to rule out the database as the cause of
> this
> problem. Moreover those machines that have problems with TCP/IP seem to
> work
> with Named Pipes (at least for a time)
>
> - How can I prove this isn't the DB?
> - Could the application, if poorly coded contribute to this problem?
> - How can I prove that the application is poorly coded?
> - How can I isolate the problem to th network? Can anyone recommend free
> easy to use network tools that can detect the network issue
>
> regards,
>
> Andre
