Re: Command Timeouts
From: Toby Herring (therring*_at_*teletrack.com)
Date: 10/05/04
- Next message: dwh2200: "RE: Obtaining Current Execution Status in T-SQL"
- Previous message: David Portas: "RE: Updating multiple tables with one statment"
- In reply to: Charles Dana: "Re: Command Timeouts"
- Next in thread: Charles: "Re: Command Timeouts"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 5 Oct 2004 13:51:45 -0400
Sorry, I meant the CommandTimeout property on the connection. Both the
ADODB.Connection and the ADODB.Command object have a CommandTimeout
property.
The query-timeout setting on the server may also be set to 30 seconds. By
default, it's set to 10 minutes, I think, but it may have been adjusted by
an administrator.
-- Toby Herring MCDBA, MCSD, MCP+SB Need a Second Life? http://secondlife.com/ss/?u=03e0e5b303c234bf08e80ee40119a65e "Charles Dana" <ctdana@slmpd.org> wrote in message news:ejcpFLwqEHA.708@tk2msftngp13.phx.gbl... > > Yes - I set the connection time to 500 seconds. > > Also, if I set the commandtimeout to something like 3 seconds, the job > still runs for 30 seconds before time out.
- Next message: dwh2200: "RE: Obtaining Current Execution Status in T-SQL"
- Previous message: David Portas: "RE: Updating multiple tables with one statment"
- In reply to: Charles Dana: "Re: Command Timeouts"
- Next in thread: Charles: "Re: Command Timeouts"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|