Re: Help: inappropriate OLEDB timeout:
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Wed, 6 Jul 2005 20:30:07 +0000 (UTC)
Matt C. (canimal@xxxxxxxxxxx) writes:
> Starting yesterday, an application that has previously run without
> problems (for several weeks now) has started throwing Timeout Expired
> errors after 30 seconds.
>
> The Command.CommandTimeout, Connection.CommmandTimeout, and
> Connection.ConnectionTimeout on the client are all set properly to values
> well in excess of 30 seconds. Also, the Connection object is using
> adUseServer for cursors.
>
> The application was developed using the SQLOLEDB provider. I have made a
> test version using the MSDASQL.1 provider, and this test version seems to
> be running OK. So there is some problem with the SQLOLEDB provider,
> apparently. (Using MSDASQL for testing is fine, but I do not want to
> switch db providers permanently unless there is no other choice.)
>
> I tried upgrading to MDAC 2.8 SP1, this didn't help. I have checked for
> lock timeouts, nope, not the problem.
>
> I am baffled. Does anyone have any ideas?
It's difficult to have any ideas about an application that I don't anything
about. All I know is that a query starts to time out after 30 seconds.
There could be plenty of reasons for this.
It could be that the data volume in the database has grown, so that the
query now takes longer time to run. Note that because of changes in
statistics, the optimizer may settle on a different query plan - most
often this is to the better, but not always.
But it could be blocking problems. It could be another process that
blocks you. But - with ADO it's possible to block yourself. This
can happen if you issue a query on a connection that is busy fetching
data from a result set. An ODBC driver or DB-Library would tell you that
the connection is busy. But ADO tries to be a nice guy and opens a
second connection behind your back. Unfortunately, SQL Server does not
know that the connections are the same, you they block each other.
If nothing of this helps you, you will need to post more information.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
.
- Follow-Ups:
- Re: Help: inappropriate OLEDB timeout:
- From: Matt C.
- Re: Help: inappropriate OLEDB timeout:
- References:
- Help: inappropriate OLEDB timeout:
- From: Matt C.
- Help: inappropriate OLEDB timeout:
- Prev by Date: Re: Linked Servers
- Next by Date: Re: Linked Servers
- Previous by thread: Help: inappropriate OLEDB timeout:
- Next by thread: Re: Help: inappropriate OLEDB timeout:
- Index(es):
Relevant Pages
|