• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 654
  • Last Modified:

lock: timeout in Profiler


I was trying to trace timeouts in Profiler on a particular database.
Using the lock: timeout parameter I would get timeouts with a LoginName of 'sa'
there would be an ObjectID, StartTime, SPID and nothing else.

sa isn't used by any process in this app and nothing else runs on the server.
All db options except AUTO_UPDATE_STATS have been turned off and I that
isn't even running when this happens.

I checked a few of our other SQL Servers and databases and the same thing
happens there too.

Why is this happening?
1 Solution
if you do a SP_WHO in query analyzer, I think you will find that several connections do show up with the SA account (lazy writer, etc)....

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now