|
|
Posted by Robert on 01/30/06 19:03
We had a situation where a user in Access left a drop down menu open all
night. The drop down menu ran a select query for 13 hours. The query only
completed when the user ended the session the next day. The focal for the
application would like SQL Server to terminate the query if it takes over 5
or 10 minutes to complete. The select statement left a lock on the table
and updates and index reorgs were held up. I think SQL sees the query as a
valid running query and the timeout is ignored.
"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns9759B9DDB75C0Yazorman@127.0.0.1...
> Robert (robert.j.sipe@boeing.com) writes:
>> Can anyone tell me what the query time out is for? It is not acting as
>> I would exepct
>
> The query timeout is for queries to remote servers. I will have to
> admit that I have not investigated the option in depth, although we
> have had cases at work where we have run into such timeouts.
>
> What are your expectations?
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|