Activity overview
Latest activity by scott47
Hi Chris,
I am still having this issue with SSMS 2008R2.
Basically if I have any servers connected in the object explorer and click the SQL Search button at the top SSMS will freeze. After that the "is Busy" button normally appears if I click any thing in the Object explorer window, although sometimes it doesn't do anything at all. Eventually I have to use task manager to manually kill that SSMS instance and just hope if I have more than one window open that I get the right one.
The size of the database doesn't appear to make any difference as I've tested this on small servers (local) to HUGE servers with tons of SQL objects. The freezing is always the same.
If I'm sure there are no servers connected in the object explorer window before I click the SQL Search button the SQL Search window opens without any issues. After it's open I can connect to as many servers in the object explorer as I want without any problems.
If I have no servers connected in the object explorer, open SQL Search, connect to a SQL server, close SQL Search and then re-open SQL Search while still connected to the server, SQL Search opens without any issues.
I also use SSMS 2014 and none of these issues occur in that environment.
Thanks!
Scott / comments
Hi Chris,
I am still having this issue with SSMS 2008R2.
Basically if I have any servers connected in the object explorer and click the SQL Search button at the top SSMS will freeze. After that th...
I have had the exact same problem (SSMS freezing when clicking SQL Search) ever since upgrading to SQL Search version 2 on 06/16/2015.
SSMS doesn't seem to freeze up every time, just most of the time. Until today I hadn't thought about searching for other users reporting this problem but I'm glad to see that I'm not the only person having this issue. So far at,my company, I am the only user that has upgraded SQL Search so I am the only person here that has this issue.
One thing I've noticed that seems to help is if there are NO databases connected in the SSMS object explorer when I open SQL Search and then I leave the SQL Search tab open I am able to use the tool. Once the SQL Search tab is opened I am able to open one or more databases without any problems (at least up to this point). If I do have one or more databases connected the first time I try to open a SQL Search tab, more often than not SSMS will freeze and I'll have to use Windows Task Manager to kill SSMS entirely.
To summarize:
Open SQL Server Management Studio
If database(s) are connected in the SSMS Object explorer and I leave them open, most of the time when I click SQL Search, SSMS Freezes.
If database(s) are connected in the SSMS Object explorer and I close them, every time I have clicked SQL Search it opens without any issues.
If no databases are connected in the SSMS Object explorer, every time when I click SQL Search it opens without any issues.
Once the SQL Search tab is open I can connect to one or many databases in the SSMS Object explore with no issues
I don't think it matters but I have the Red Gate developer suite installed.
Thanks!
Scott / comments
I have had the exact same problem (SSMS freezing when clicking SQL Search) ever since upgrading to SQL Search version 2 on 06/16/2015.
SSMS doesn't seem to freeze up every time, just most of the ti...