Re: command timeout does not work
- From: "rani" <raniz@xxxxxxxxx>
- Date: Thu, 16 Jun 2005 10:29:21 +0300
Sorry, I haven't mentioned it the CursorLocation = adUseClient
and yes the result is in this state of things (I must use this
CursorLocation).
Thanks Rani
"Val Mazur (MVP)" <group51a@xxxxxxxxxxx> wrote in message
news:ugxbulicFHA.2288@xxxxxxxxxxxxxxxxxxxxxxx
> Have you tried to open Recordset on a client side? Same result?
>
> --
> Val Mazur
> Microsoft MVP
>
> http://xport.mvps.org
>
>
>
> "rani" <raniz@xxxxxxxxx> wrote in message
> news:uHeq3uXcFHA.2076@xxxxxxxxxxxxxxxxxxxxxxx
> > Thanks Val for the answer
> > I tried both ways either by Executing through the command object or by
> > openning the Recordset passing the command object, and still no results
> > (no
> > timeout).
> > Only after about 4 minutes the query times out.
> > any other idead?
> > Thanks Rani
> >
> >
> > "Val Mazur (MVP)" <group51a@xxxxxxxxxxx> wrote in message
> > news:u63A%23eTcFHA.2664@xxxxxxxxxxxxxxxxxxxxxxx
> >> Hi,
> >>
> >> How do you execute your SP? Are you using Execute method of Command or
> >> Connection object?
> >> Also check if this is not your case
> >>
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;188858
> >>
> >> --
> >> Val Mazur
> >> Microsoft MVP
> >>
> >> http://xport.mvps.org
> >>
> >>
> >>
> >> "rani" <raniz@xxxxxxxxx> wrote in message
> >> news:%23ZPZimQcFHA.3488@xxxxxxxxxxxxxxxxxxxxxxx
> >> > Hello,
> >> > I'd appreciate a hint as to how to solve the problem, if anyone
heard,
> > or
> >> > bumped into one like this:
> >> >
> >> > I'm running a Stored procedure using ADO 2.6 VB6 against sql server
> > 2000.
> >> > I'm using the default commandTimeout (30 sec.), but I don't get the
> >> > expected
> >> > "timeout expired" exception after the 30 seconds. Within the stored
> >> > procedure it runs another stored procedure using "sp_executesql".
> >> > The 2nd Stored Procedure returns a Record, while the 1st is not
> > selecting
> >> > anything. The two stored procedures run on two different servers
which
> > are
> >> > linked servers.
> >> >
> >> > The ADO query does not run in Transaction nor does any transaction
> > opened
> >> > in
> >> > any of the stored procedures.
> >> > SET NOCOUNT ON is set in both Stored procedures.
> >> > The 2nd stored procedure runs a "heavy" query creating many temporary
> >> > tables
> >> > (#table), inserting data and updating in these tables.
> >> >
> >> > Does anyone have a clue of why I don't get the timeout on time?
> >> >
> >> > Is it possible that ADO waits more than 30 sec. for some kind of
> > rollback
> >> > to
> >> > take place?
> >> >
> >> > Thanks Rani
> >> >
> >> >
> >>
> >>
> >
> >
>
>
.
- References:
- command timeout does not work
- From: rani
- Re: command timeout does not work
- From: Val Mazur \(MVP\)
- Re: command timeout does not work
- From: rani
- Re: command timeout does not work
- From: Val Mazur \(MVP\)
- command timeout does not work
- Prev by Date: Re: converting String to VARIANT type
- Next by Date: escaping semi colon in connectionstring
- Previous by thread: Re: command timeout does not work
- Next by thread: ADO Updates sometimes failing, causing connection timeouts?
- Index(es):
Relevant Pages
|
|