SQL Search text box grayed out in SSMS. How to resolve?

LRush

Just installed SQL Server Toolbelt Essentials and having issues whereby the SQL Search text box is grayed out in SSMS and thus I am unable to use the search utility.    Is there a resolution to this?    I believe we are using the latest version of SQL Search.

SQL Search version:   3.2.6.2313

SSMS 2016:  13.0.15000.23

LRush

We resolved our issue by upgrading SSMS to:

SSMS version to 13.0.16106.4, (SSMS 16.5.3)

cthtyler

I am having the same issue. I am running SSMS 18.2. Does Sql Search support this version?

Ptwb

This is happening to me as well on SSMS 18.2.  I was on SSMS 16.  Installed SSMS 18.2.  Then noticed I didn't have any of my red gate stuff.  So I got SqlSource and SqlPrompt into 18.2. Everything was working well.   Just now, I needed SqlSearch.  Only way to get it was to uninstall it and reinstall SqlSearch.  Now I see SqlSearch in my 18.2 but SSMS is now worthless.  Switching tabs, the contents don't update reliably.  I can't even use SqlSearch as everything is grayed out.  Is it indexing? I see an option to cancel indexing, but it seems to do nothing.

Now I am trying to get SqlSearch out of my 18.2. 

woj123

I had the same problem in SSMS 18.2 and SQL Search 3.3.  Often you'll have an add-in like SSMSBoost that will open connections to Database Engines automatically upon start up of SSMS.  The answer for me was to let that happen, but then open SQL Search, and THEN open another connection to a Database Engine.  That will "light up" SQL Search and you will be able to use it normally.

Axemagus

This still appears to be broken with SSMS 18.4 and SQL Search 3.4.  Following the instructions posted by woj123 works, but is a needlessly complicated process to follow every time I launch SSMS & want to use SQL Search.

PhilB

yep i have given up on SQL search in SSMS 18.2  I guess you get what you pay for - free tool - no workie

Mansharma

I was getting the same issue in SSMS 18.5 with SQL Search 3.5.0.2590. For me, running SSMS as Administrator solves the issue.

jtwite

As woj123 said, I found just disconnecting from the server in SSMS's Object Explorer, then re connecting (via Registered Server makes this reasonably painless) fixes the issue.  Looks like it is SQL Prompt's tab-auto re-connect that forgets to also do the SQL search tab

ClaireP

jtwite said:

As woj123 said, I found just disconnecting from the server in SSMS's Object Explorer, then re connecting (via Registered Server makes this reasonably painless) fixes the issue.  Looks like it is SQL Prompt's tab-auto re-connect that forgets to also do the SQL search tab

THANK YOU!!!!

cbasoz

Mansharma said:

I was getting the same issue in SSMS 18.5 with SQL Search 3.5.0.2590. For me, running SSMS as Administrator solves the issue.

Thanks! Running as admin fixes it.

vadim3108

woj123 said:

I had the same problem in SSMS 18.2 and SQL Search 3.3.  Often you'll have an add-in like SSMSBoost that will open connections to Database Engines automatically upon start up of SSMS.  The answer for me was to let that happen, but then open SQL Search, and THEN open another connection to a Database Engine.  That will "light up" SQL Search and you will be able to use it normally.

Thanks dude!
Works perfectly! just open another connection as woj123 sais, from File->Connect Object Explorer