Extremely High Lock Timeouts

I have recently been investigating some server issues and
found that at certain times of the day we our
experiencing lock timeouts in 10,000 per second. Our
lock timeout value is set to -1, which to me means that
the locks should never timeout.
We are not experiencing an deadlocks during these times
and all lock timeouts are key locks.
Can anyone clear this up for me.
There are lots of internal synchronization protocols which request locks
with a 0 length timeout. These are refered to as "NoWait" locks. That is, if
SQL Server can get the lock now, great, otherwise if it can't get the lock
it'll do something different. Unfortunately, these show up in profiler as
lock timeouts when they're really just part of the normal internal locking
protocols. (SQL Server has no way of knowing at the profiler level).
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jeremy" <anonymous@.discussions.microsoft.com> wrote in message
news:1ce5d01c4532b$c5ea1cd0$a101280a@.phx.gbl...
> I have recently been investigating some server issues and
> found that at certain times of the day we our
> experiencing lock timeouts in 10,000 per second. Our
> lock timeout value is set to -1, which to me means that
> the locks should never timeout.
> We are not experiencing an deadlocks during these times
> and all lock timeouts are key locks.
> Can anyone clear this up for me.