I am tracing a SQL Server 2000 production server that gets a query
about every second. The Event I chose to watch was "Lock:Timeout". To
my surprise I see many of these come through the trace. Is this normal
behavior? What is "Lock:Timeout" showing me?

Thanks,
John

(john.livermore@inginix.com) writes:
> I am tracing a SQL Server 2000 production server that gets a query
> about every second. The Event I chose to watch was "Lock:Timeout". To
> my surprise I see many of these come through the trace. Is this normal
> behavior? What is "Lock:Timeout" showing me?

Apparently there is a lot of lock timeout events generated internally.
If you cannot associate the events with a database or stored procedure
in your application, I should not be worried.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

If the purpose of your trace is to monitor long-term blocking, consider
using the LockAcquired event class with a non-zero duration (e.g. 1000).

--
Hope this helps.

Dan Guzman
SQL Server MVP

<john.livermore@inginix.com> wrote in message
news:1110217321.010759.4060@z14g2000cwz.googlegrou ps.com...
>I am tracing a SQL Server 2000 production server that gets a query
> about every second. The Event I chose to watch was "Lock:Timeout". To
> my surprise I see many of these come through the trace. Is this normal
> behavior? What is "Lock:Timeout" showing me?
>
> Thanks,
> John
>