|
|
Posted by Erland Sommarskog on 10/01/28 11:40
Ryan (ryanofford@hotmail.com) writes:
> We have two applications (1 on two servers and 1 on another). Every so
> often, we 'lose' the connection to the SQL database which in effect
> takes these applications down. One app is a service (written in Delphi)
> , the other is a web page (ASP).
>
> From what I can tell, both different methods use the same port (1433)
> to access the data and create an open connection. We can telnet to this
> before a problem and suspect that we can't afterwards.
>
> I can however, connect through EM (I really do need to confirm if this
> remains available) and I can see a trace running on the SQL server even
> when the problems occur (the trace is to see if SQL is still doing
> something). I am under the impression that the SQL server is fine, but
> does anyone know what port EM and SQL Profiler use ? If it's something
> different, then that would explain some of it.
>
> I think there is a network problem on this specific port, but that
> others are OK. I'm a bit rusty on this, so please be gentle with any
> replies. :-)
Profiler and EM and everyone else operates on the same port. Unless,
they are on the same machine as SQL Server, in which case they
typically use Shared Memory?
And in any case, network problems usually to not conern a single
port.
On what machines are EM and Profiler?
To me it sounds like you have glitches in your network. A short drop
in the connection may be fatal for a tool that does not handle it
well. (Which for instance Query Analyzer does. EM may also be
reconnecting silently, if it finds the connection dead.)
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|