Re: SELECT statement (Time Out)
From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 07/09/04
- Next message: Partha Mandayam: "Re: Not a trusted connection"
- Previous message: Denis Crotty: "Re: Not a trusted connection"
- In reply to: Zach Wells: "Re: SELECT statement (Time Out)"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 9 Jul 2004 18:21:19 -0400
Right, you get a message if your the victim since SQL Server kills you.
-- Andrew J. Kelly SQL MVP "Zach Wells" <no_zwells_spam@ain1.com> wrote in message news:%233S1plfZEHA.3092@tk2msftngp13.phx.gbl... > Andrew J. Kelly wrote: > > > Zach, > > > > That is true the select statement itself will not timeout but the connection > > will. So if the select is blocked and it is blocked for longer than the > > connection timeout setting the connection will be terminated. This can make > > people think the select is what timed out. > > > > I understand. My point was that, depending on where you run your query > from, if you're blocked, it could sit there indefinitely. However, if > you're deadlocked, you'll get a message as soon as you are deadlocked. > (for example, QA defaults to no timeout so will hang indefinitely if the > query is blocked). > > Zach
- Next message: Partha Mandayam: "Re: Not a trusted connection"
- Previous message: Denis Crotty: "Re: Not a trusted connection"
- In reply to: Zach Wells: "Re: SELECT statement (Time Out)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|