Connection timed out

We are running SQL Server 2000 Version 8.00.760. We are running our
application using Java. We are frequently getting Connection Timed Out in
our appserver. Is anyone aware of such an issue this version of SQL Server
? We have similar configurations on several other servers, but only the
appserver's connected to this particular database is giving connection
timeouts. Is this a known bug ? or are we hit with a virus ?
I searched Google, but did not find any info.
-Nags
Nags,
The "application timeout" usually means that the driver or the client code
has some sort of timeout within which, if sql server doesnt execute and
return the query, then it times out. For example, I think the default at
the ODBC driver setting is 30 seconds.
That leads us to the next question - why is it taking 30 seconds or more
(I'm making the assumption here that 30 sec is your default timeout as
well). I'm also making another assumption - that the other configurations
you have are EXACTLY like this "problem server" configuation which includes
the same amt of tables, and the same amt of data in these tables. And that,
there was a time maybe when things were fine on this "problem" server.
A couple of things you'd want ot check -
1. Does this happen for any query/hit against the sql server? example, even
logging on (user name/password) results in a timeout?
2. Does it happen for a set of queries?
3. If you know the queries that are commonly executed by this application,
OR some of the queries that you've seen timeout. Take those queries in
Query analyser and see how long they run.
4. Try updating statistics on the tables.
5. Compare index structures on the tables on the 'good' db's with their
counterparts on this problem db.
Hope this helps.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
|||I'm facing the pro as well.
I look into error log, it said 'Server terminating due to 'Stop' request
from Service Control Manager'. The db server also using the Autogrowth
option, and everytime it growing the log file, seems like the server stop
responding.
Pls advise.
Thanks in advance.
"Vikram Jayaram [MS]" wrote:

> Nags,
> The "application timeout" usually means that the driver or the client code
> has some sort of timeout within which, if sql server doesnt execute and
> return the query, then it times out. For example, I think the default at
> the ODBC driver setting is 30 seconds.
> That leads us to the next question - why is it taking 30 seconds or more
> (I'm making the assumption here that 30 sec is your default timeout as
> well). I'm also making another assumption - that the other configurations
> you have are EXACTLY like this "problem server" configuation which includes
> the same amt of tables, and the same amt of data in these tables. And that,
> there was a time maybe when things were fine on this "problem" server.
> A couple of things you'd want ot check -
> 1. Does this happen for any query/hit against the sql server? example, even
> logging on (user name/password) results in a timeout?
> 2. Does it happen for a set of queries?
> 3. If you know the queries that are commonly executed by this application,
> OR some of the queries that you've seen timeout. Take those queries in
> Query analyser and see how long they run.
> 4. Try updating statistics on the tables.
> 5. Compare index structures on the tables on the 'good' db's with their
> counterparts on this problem db.
> Hope this helps.
> Vikram Jayaram
> Microsoft, SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
>
>