I have updated SSMS to v18.5 and then uninstall SQL Search, downloaded the latest one and installed. SSMS started, I click button "SQL Search" - no any errors/exceptions but SQL Search does not start. I have repeated these actions on 2 workstations W7 and W10. The same result. How to fix it?
Asked
Active
Viewed 9,629 times
17
-
Is there anything in the log file (`%localappdata%\Red Gate\Logs\SQLSearch 3`) that might show what the problem is? – adrianbanks Apr 17 '20 at 14:16
-
Having the same issue, just updated ssms to 18.5 and SQL search won't open. Nothing in the logs as well. – Umair Apr 17 '20 at 22:19
-
Because this is top on Google: if in someone's case, it DOES start but is greyed out, disconnect object explorer and then reconnect to make it work. – aderchox Jan 11 '22 at 06:28
4 Answers
33
Ok there is some issue with SQL Search version 3.0, but when I tried SQL Search version 3.5 it is working fine. Download it from here: v3.5.2.2607
More details here
Newer versions of SQL Search are listed here.

Umair
- 4,864
- 3
- 28
- 47
-
3Thanks, the problem is that the default download page points still to version 3.4. https://www.red-gate.com/products/sql-development/sql-search/installer/ – Vojtěch Dohnal Jul 08 '20 at 10:48
-
3.5 works for me too. Not sure why the download from RedGate is 3.4 though. – nonpoliticaltag Aug 25 '20 at 23:38
-
1
-
1
-
1I think @SQLJax is trying to say that the default download from the Redgate site is still 3.4x and broken. I am surprised that they haven't updated it yet. – Shashank Shekhar Sep 10 '20 at 21:03
-
Got it... Yes, it's surprising they have not yet updated even though they know and replied to a similar issue on their own forums. – Umair Sep 10 '20 at 21:07
-
1
Try to install this version : https://download.red-gate.com/checkforupdates/SQLSearch/SQLSearch_3.5.0.2590.exe
It works fine for me

Yassine
- 331
- 1
- 3
- 9
0
I'm seeing the same issue in SQL Search 3.5.5.2703
The Redgate Forums have this workaround which worked for me:
I think you are running into an issue we are aware of and working on. Apologies for the hassle! As a workaround, could I ask you to try the following?
- disconnect your SQL server from SSMS Object explorer
- Close and reopen SQL Search
- Reconnect your SQL Server

SinisterPenguin
- 1,610
- 15
- 17