Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ferrethouse
Constraint Violating Yak Guru
352 Posts |
 Posted - 2012-03-28 : 12:35:08
|
| I rarely see significant waits of this type but between 8am and 9am this morning we had a huge wait of this type that appeared to affect our "Students" table. I don't know how to track down what caused this lock. The "Ignite" software I'm using shows the queries that were blocked by this lock but it doesn't seem to reveal what caused the lock. How do I track this down? It doesn't seem to be an ongoing thing and I don't know if it will happen again but it did cause application downtime this morning so I'd like to know what happened.Thanks,Craig |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2012-03-28 : 12:44:16
|
| Query sys.dm_exec_request, there's a column blocking session id. It contains the session id of the session that's holding the blocking lock. Not after the fact though, just during the blocking.Sure Ignite doesn't show the blocking session? That would be a very strange limitation.--Gail ShawSQL Server MVP |
 |
|
|
ferrethouse
Constraint Violating Yak Guru
352 Posts |
Posted - 2012-03-28 : 15:04:18
|
quote:
Originally posted by GilaMonster
Sure Ignite doesn't show the blocking session? That would be a very strange limitation.--Gail ShawSQL Server MVP
It does! I didn't even notice that. That's great. Thanks so much. |
|
|
|
|
|
|
Tracking down cause of LCK_M_IX