command timeout does not work
- From: "rani" <raniz@xxxxxxxxx>
- Date: Tue, 14 Jun 2005 20:52:09 +0300
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
.
- Follow-Ups:
- Re: command timeout does not work
- From: Val Mazur \(MVP\)
- Re: command timeout does not work
- Prev by Date: Re: jro.CompactDatabase stopped working
- Next by Date: ADO Updates sometimes failing, causing connection timeouts?
- Previous by thread: transaction access and vb
- Next by thread: Re: command timeout does not work
- Index(es):
Relevant Pages
|