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?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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)....

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.