command timeout does not work



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


.



Relevant Pages

  • Re: Adding date to parameter
    ... ClaimedDate does appear to have a properly formatted date. ... I am using the following stored procedure: ... -- SET NOCOUNT ON added to prevent extra result sets from ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Using DTS to Insert 1 Second record for every second in a month?
    ... Okay...so you basically need a calendar table by seconds. ... And yes that will perform pretty fast for the type of query ... >set NoCount OFF ... >This stored procedure took about 21 minutes. ...
    (microsoft.public.sqlserver.dts)
  • Re: Adding date to parameter
    ... and SqlClient with dates, but I don't think I could rewrite the code in a ... I am using the following stored procedure: ... -- SET NOCOUNT ON added to prevent extra result sets from ...
    (microsoft.public.dotnet.framework.adonet)
  • RE: What stored procedures call this stored procedure?
    ... this in the wrong way - I have the ID of a stored procedure and I'm looking ... > set nocount on ... > declare @rv int ...
    (microsoft.public.sqlserver.programming)
  • Re: Returning results from a temporary table using ADO
    ... you need to add SET NOCOUNT ON as a very first statement ... which is treated as a resultset (recordset) by OLEDB ... > I 'm trying to invoke a stored procedure using ADO from a web page. ...
    (microsoft.public.vb.database.ado)