• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3938
  • Last Modified:

Timeout while running SQL Stored Procedure

I am running SQL Server 2005.  As far as I can tell the remote query timout for the server (all databases) is 600 seconds.

I am running an Access front-end with the following connection string:
Provider=sqloledb;Data Source=n.n.n.n;Initial Catalog=DBName;Connection Timeout=600;UID=myuserid;PWD=mypwd

When I run a stored procedure that will take at least 1 minute, it always times out after 30 seconds.  What am I missing?
  • 2
2 Solutions
Time out is buried in SQL Server Management Studio

Management Studio > Tools > Options > Designers

Change the default transaction time out there.
wsturdevAuthor Commented:
I went there and changed it to 600 seconds, and the timeout still happens after 30 seconds.

Also, are you saying there would be no way to set the timeout to "normal" and override it when needed?
What is the exact timeout message?
Guy Hengel [angelIII / a3]Billing EngineerCommented:
>Provider=sqloledb;Data Source=n.n.n.n;Initial Catalog=DBName;Connection Timeout=600;UID=myuserid;PWD=mypwd
you set the connection timeout, but what you need is the command timeout, which is also 30 seconds by default.

using the adodb.command object, set the commandtimeout property of that object to 600 before executing the command (procedure)

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now