|
|
Posted by Erland Sommarskog on 07/06/07 22:22
M Bourgon (bourgon@gmail.com) writes:
> I do.
> Msg -2, Level 11, State 0, Line 0
> Timeout expired. The timeout period elapsed prior to completion of
> the operation or the server is not responding.
>
> Looking at what Mohit posted, my server does have the remote query
> timeout of 600 seconds. But this is the first time I've ever seen
> this issue. Odd.
>
> Okay - this is odd - if I create a new Database Engine Query, it works
> properly, even though (with the same instance of SSMS running) I
> managed to have it timeout on me with the WAITFOR test.
>
> So, is that why Query Analyzer doesn't get killed after 10 minutes?
> Because it's a local connection?
> Or did you just manage to create a bug separate from what I was
> seeing?
I don't think the configuration option that Mohit mentioned has anything
to do with it. Since I know that it has the default of 10 minutes, it
was the first thing that came into my mind, but two things led me to
believe that it was not involved: 1) you did not get the error in QA.
2) The negative message number -2 is likely to be generated by Mgmt Studio
itself.
But apparently Mohit's question was useful, as it inspired Aaron to ask
the right question.
--
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]
|