Re: Help: inappropriate OLEDB timeout:
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Thu, 7 Jul 2005 21:09:47 +0000 (UTC)
Matt C. (canimal@xxxxxxxxxxx) writes:
> I believe I've sorted this out. It is a combination of two things: the
> MDAC hotfix described in kb article 832483, and setting the
> CommandTimeout to a large value ( > 65536).
>
> On PCs that have the hotfix applied, when the CommandTimeout is set to
> 65537, I get the premature 30 second timeout. When it's set to 65534,
> there is no premature timeout and the process completes normally.
The default timeout of 30 seconds is evil. I wonder how much grief
and money it costs all over the planet?
In theory at least, a timeout of 0, should give you an inifinite timeout,
but I seem to recall reports of ADO not always respecting this.
The funny thing is that if you program against the OLE DB API directly,
the default for the timeout in SQLOLEDB is 0.
--
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.
- Re: Help: inappropriate OLEDB timeout:
- From: Erland Sommarskog
- Re: Help: inappropriate OLEDB timeout:
- From: Matt C.
- Re: Help: inappropriate OLEDB timeout:
- From: Matt C.
- Help: inappropriate OLEDB timeout:
- Prev by Date: Re: Help: inappropriate OLEDB timeout:
- Next by Date: Re: Help: inappropriate OLEDB timeout:
- Previous by thread: Re: Help: inappropriate OLEDB timeout:
- Next by thread: Re: Help: inappropriate OLEDB timeout:
- Index(es):
Relevant Pages
|