Re: timeout
From: Narayana Vyas Kondreddi (answer_me_at_hotmail.com)
Date: 07/05/04
- Next message: Narayana Vyas Kondreddi: "Re: Managing Disk Space"
- Previous message: John Bell: "Re: Roles & Users"
- In reply to: Rob: "timeout"
- Next in thread: Rob: "Re: timeout"
- Reply: Rob: "Re: timeout"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 5 Jul 2004 22:42:14 +0100
In your VBScript file you have to increase the default timeout (30 seconds)
to more than a minute. You have to change the CommandTimeout property of
your command/connection object. the Query timeout value in Enterprise
Manager, is for Enterprise Manager and is not relavant when running your
VBScript. You might want to have a look at the following articles:
http://vyaskn.tripod.com/sql_odbc_timeout_expired.htm
http://vyaskn.tripod.com/watch_your_timeouts.htm
-- Vyas, MVP (SQL Server) http://vyaskn.tripod.com/ "Rob" <anonymous@discussions.microsoft.com> wrote in message news:274f901c462c5$9573cc50$a301280a@phx.gbl... > Hello All, > > I have a vb script that verifies if a specific service is > running, if yes, then it runs a sql stored proc. > The stored proc takes about 1 minute to run when launched > from QA. > However, when launched through the vbscript file, I get a > Timeout Expired from MS OLE DB Provider for SQL Server > error. > Query-timeout in Enterprise is set to 0. > > I can post a script if needed, but, doesn't seem to be a > syntax problem. > Any thoughts are appreciated, > R >
- Next message: Narayana Vyas Kondreddi: "Re: Managing Disk Space"
- Previous message: John Bell: "Re: Roles & Users"
- In reply to: Rob: "timeout"
- Next in thread: Rob: "Re: timeout"
- Reply: Rob: "Re: timeout"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|