Home Dashboard Directory Help
Search

SSMS 2012 SP1 stops responding whenever I try to modify an SP, trigger, etc by FishermanDBA


Status: 

Closed


1
0
Sign in
to vote
Type: Bug
ID: 800264
Opened: 9/11/2013 8:16:53 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I am continually having an issue with SSMS 2012 hanging (not Responding) when I try to open files, sp's, triggers, or sometimes query windows. I have tried to reinstall, repair, and upgraded to SP1 with no effect. I have gone through the settings to see if there was something awry. I am at a loss. It appears to be happening to one server and potentailly one database.

The database in question is set to a compatibility level of 90 (2005). However I restore the backup to another server with no issues in SSMS. I am able to open and modify files, sp, trigger... in the restored database without an issue. The issue just started happening a couple months ago after nearly a year of running just fine.

When it first started I hit some keys that separated the windows and the issue window had a connection window. When I cancelled the connection login window the tab started responding, but I have been unable to get to the stage again. It may be that it is trying to connect to the database and is hanging there?

any help or suggestions would be greatly appreciated.

Details
Sign in to post a comment.
Posted by Microsoft on 9/24/2013 at 2:51 PM
Hello Fisherman.
This appears to be a support issue rather than a product bug. Please follow the included link below to get in touch with a Microsoft Support Engineer who will be able to further assist you.
https://support.microsoft.com/oas/default.aspx?Gprid=1044&st=1&wfxredirect=1&sd=gn&wfxredirect=1
-Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by Sethu Srinivasan on 9/17/2013 at 1:30 PM
Hello,
Thanks for reporting this issue. Do you see this issue when you detach and re-attach the same database?. Would it be possible for you to share the detached database and log file for us to investigate this issue?

Thanks
Sethu Srinivasan [MSFT]
Sign in to post a workaround.