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 |
|
coolerbob
Aged Yak Warrior
841 Posts |
 Posted - 2005-08-18 : 08:49:09
|
| I sometimes have a problem where a statement is taking for ever. After a while I realize that the reason why I am having problems is because I have an uncommitted transaction on the same table on another connection. Is there a quick way that I could check if there are any uncomitted transactions on any connections? |
|
|
mwjdavidson
Aged Yak Warrior
735 Posts |
Posted - 2005-08-18 : 08:58:11
|
| DBCC OPENTRAN |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-08-18 : 09:08:46
|
| Note that DBCC OPENTRAN won't tell you if you have a BEGIN TRANSACTION that hasn't done any work as yet - e.g. a SELECT ... WITH (HOLDLOCK) - even if that is blocking an UPDATE in a transaction block.Kristen |
|
|
|
mwjdavidson
Aged Yak Warrior
735 Posts |
Posted - 2005-08-18 : 09:51:31
|
| Good point Kristen. Just remembered also that it only returns the oldest open transaction...Mark |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2005-08-18 : 11:58:49
|
| "Good point Kristen""Pedantic" would be a better description I think!Kristen |
|
|
|
|
|
|
Freeze due to uncomitted transaction