May 9, 2007 at 12:18 pm
I've come across an intermittent problem with SQL Management Studio that I think you should be aware of.
The symptoms are that users start reporting timeouts on database connections and there are locks on certain user tables.
Looking at master..sysprocesses reveals that SQL Management Studio is doing the blocking but the query it is trying to run is quite innocious.
On attempting to close a SQL Management Studio window you get a warning message asking you if you want to commit or rollback open transactions and yet you never began any.
running SELECT @@TRANCOUNT will tell you that there are no open transactions and yet choosing to commit or rollback suddenly brings you database back from the dead.
This is particularly nasty as I first came across it during a high pressure 05:00 LIVE deployment.
May 9, 2007 at 1:30 pm
Thanks for sharing this with us. Care to write a small article about this one and submitting it to Steve ?
May 12, 2007 at 7:04 am
I don't really have any more to add than what is in the post. I need to pin it down further before I have enough to go into an article
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply