Prev: Stored proc issue after converting from Sql Server 2000 to 2005.
Next: DBCC CHECKTABLE error
From: JPK on 17 Jul 2008 13:54
I am getting this error "Timeout expired. The timeout period elapsed prior
to completion of the operation or the server is not responding." And this
error pops up in 30 seconds. Now the Sertver timeout is set to 600 seconds
or 10 minuted yet this is timing out in 30 seconds. Any ideas how to extend
the timjeout poast 30 seconds??


thanks,

JIM

From: Denny Cherry on 17 Jul 2008 14:04
The server timeout which you have set for 600 seconds is either the
connection timeout (how long it takes to connect to the SQL Server) or
the remote query timeout (for queries over linked servers).

There isn't any setting to override that timeout. It's hard coded in
SQL Enterprise Manager. Run the same query within Query Analyzer and
it will continue to run until it completes.

Denny

On Thu, 17 Jul 2008 12:54:54 -0500, "JPK" <james(a)klett.us> wrote:

>I am getting this error "Timeout expired. The timeout period elapsed prior
>to completion of the operation or the server is not responding." And this
>error pops up in 30 seconds. Now the Sertver timeout is set to 600 seconds
>or 10 minuted yet this is timing out in 30 seconds. Any ideas how to extend
>the timjeout poast 30 seconds??
>
>
>thanks,
>
>JIM
From: Bob Beauchemin on 17 Jul 2008 14:01
Where is the error occurring? And is this a Command.Timeout or a
Connection.Timeout? Where is the "server timeout set for 600 seconds"?

Cheers,
Bob Beauchemin
SQLskills

"JPK" <james(a)klett.us> wrote in message
news:450CA353-9179-469E-9674-2E58D983D5B8(a)microsoft.com...
>I am getting this error "Timeout expired. The timeout period elapsed prior
>to completion of the operation or the server is not responding." And this
>error pops up in 30 seconds. Now the Sertver timeout is set to 600 seconds
>or 10 minuted yet this is timing out in 30 seconds. Any ideas how to
>extend the timjeout poast 30 seconds??
>
>
> thanks,
>
> JIM


From: Russell Fields on 17 Jul 2008 14:03
Jim,

You are seeing this on the client side, which means that it is probably the
ADO setting, which defaults to timing out after 30 seconds. You can set
this timeout to longer (e.g. 60 seconds) or forever (i.e. 0) as you see fit.
E.g.

myConn.CommandTimeout = 0

RLF

"JPK" <james(a)klett.us> wrote in message
news:450CA353-9179-469E-9674-2E58D983D5B8(a)microsoft.com...
>I am getting this error "Timeout expired. The timeout period elapsed prior
>to completion of the operation or the server is not responding." And this
>error pops up in 30 seconds. Now the Sertver timeout is set to 600 seconds
>or 10 minuted yet this is timing out in 30 seconds. Any ideas how to
>extend the timjeout poast 30 seconds??
>
>
> thanks,
>
> JIM


From: Plamen Ratchev on 17 Jul 2008 14:06
There is connection timeout (which you probably mean is set to 600 seconds)
and command timeout. The command timeout matters when executing a query. If
this is client code you have to set the CommandTimeout property:
http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlcommand.commandtimeout.aspx

HTH,

Plamen Ratchev
http://www.SQLStudio.com

 |  Next  |  Last
Pages: 1 2
Prev: Stored proc issue after converting from Sql Server 2000 to 2005.
Next: DBCC CHECKTABLE error