Re: Timeout - @@LOCK_TIMEOUT
From: wei xiao [MSFT] (weix_at_online.microsoft.com)
Date: 12/08/04
- Next message: wei xiao [MSFT]: "Re: blocking caused from SQL with (nolock) hint"
- Previous message: Joe K..: "Maximum Worker Threads"
- In reply to: OJ: "Re: Timeout - @@LOCK_TIMEOUT"
- Next in thread: OJ: "Re: Timeout - @@LOCK_TIMEOUT"
- Reply: OJ: "Re: Timeout - @@LOCK_TIMEOUT"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 8 Dec 2004 15:22:35 -0800
As an optimization, SQL Server internally needs to check if a transaction
can acquire some locks without waiting. When this fails, the lock timeout
event is generated (with a duration of 0) but SQL Server will wait for the
lock instead.
The value of the "Duration" column indicates for how long SQL Server waits
before the timeout. If the value is 0, then this is the internal no-wait
timeout.
-- Wei Xiao [MSFT] SQL Server Storage Engine Development http://weblogs.asp.net/weix This posting is provided "AS IS" with no warranties, and confers no rights. "OJ" <anonymous@discussions.microsoft.com> wrote in message news:193d01c4dd59$34acbc60$a501280a@phx.gbl... > I'm not sure how this can help, but here it is (one of > many examples): > > row_number=188337 > event_class=27 > text_Data=NULL > Binary_data=0x000707000DD07C4F23006F01DE541AB4 > DatabaseID=14 > HostName=PROD1 > SPID=73 > ObjectID=1333579789 > IndexID=30 > Mode=3 > > > Also, some of them are caused by SPID lower than 50, and > mode in that case is: 5. > > Thanks, > OJ > >>-----Original Message----- >>This event is generated by a low level system component. > Please post the >>entire event data column for us to understand the > situation. >> >>-- >>Wei Xiao [MSFT] >>SQL Server Storage Engine Development >>http://weblogs.asp.net/weix >> >>This posting is provided "AS IS" with no warranties, and > confers no rights. >> >>"OJ" <anonymous@discussions.microsoft.com> wrote in > message >>news:200b01c4dca6$c0f48a30$a301280a@phx.gbl... >>> Hi, >>> Trace file which I have here, contains many Lock: > Timeout >>> events. I don't understand how is it possible when >>> @@LOCK_TIMEOUT is set to -1 for all connections. >>> Thanks, >>> OJ >> >> >>. >>
- Next message: wei xiao [MSFT]: "Re: blocking caused from SQL with (nolock) hint"
- Previous message: Joe K..: "Maximum Worker Threads"
- In reply to: OJ: "Re: Timeout - @@LOCK_TIMEOUT"
- Next in thread: OJ: "Re: Timeout - @@LOCK_TIMEOUT"
- Reply: OJ: "Re: Timeout - @@LOCK_TIMEOUT"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|