When I used "sp_lock" I found that literally hundreds of exclusive locks (X) were placed on tempdb. When I attempted to look at the database properties using SSMS, the attempt timed out -- yet the normal user seemed largely unaffected by this situation. Question: what sql profiler counter(s) could shed light on the source of this locking? (While many statements can use tempdb why would so many remain in tempdb (per DBCC INPUTBUFFER)? Is it possible these statements are blocking each other in tempdb?)
TIA,
edm2