We're currently looking into this problem but in the mean time, I'd suggest rolling back to version 3.0.4 if you're affected. You can download it here.
I'm not able to reach that file (3.0.4). Not sure if it's my company's firewall.
"This site can’t be reached"
Please find here an alternative download location for SQL Search 3.0.4, this is an https link so hopefully you will not have the same issues as before. This is a temporary link that will expire in a few days:
When I downloaded SQL Search 3.0.4 I received the error message, " The Add-in supporting this command could not be loaded." At that point SQL Search was inoperable and I had uninstall it and re-install everything from the bundle.
Just to let you know that the team are currently working on SQL Search replacing the index components which will be available in a later version, possibly V3.0.8 or the release after this.
NOTE: updated version released since this post. Check further down the page.
Thanks for your post.
We do not have a fixed time for resolution on this yet but the development team are working on it.
For now we recommend reverting to SQL Search version 3.04
You can get it from my link below.
Am I the only one having issues? It just keeps "indexing" forever and never finishes. I tried this on two computers and different servers. On a different computer, I used an older version and indexing was seconds.
The only issue is that it sometimes does not refresh the results after my search. I need to toggle on and off the "Match whole words only" checkbox in order to see the results my the search.
But the good news is that the search is back accurate, previous version was certainly dangerous. Thanks RG for the fix and for the new wildcard search functionality you brought with it.
Am I the only one having issues? It just keeps "indexing" forever and never finishes. I tried this on two computers and different servers. On a different computer, I used an older version and indexing was seconds.
I confirm glfores' issue. Start it up, indexing is fairly quick against my local database. Much slower against remote and Azure. Also seems to reindex every time the server is changed, so switching back and forth is difficult.
Then, against a remote server on which I only have permissions for a single database, the "indexing forever" issue begins. Nothing can stop it. Disconnect from the remote server. No change. Disconnect from all servers. No change. Close the Search tab. Reopen. Still "indexing."
Have to restart SSMS to get back to ground zero. Since 95% of the time I'm using this against my local development DBs, it's not a showstopper (yet), but it's definitely an issue.
As far as accuracy goes--in my initial tests, this release seems to have solved the original problem.
@RichardL - I updated the latest version of SSMS (that came out just a few days ago) and the latest build of SQL Search is working fine now. I'd recommend the others update their SSMS too (@Jason Hannas)
Comments
I'm not able to reach that file (3.0.4). Not sure if it's my company's firewall.
"This site can’t be reached"
Please find here an alternative download location for SQL Search 3.0.4, this is an https link so hopefully you will not have the same issues as before. This is a temporary link that will expire in a few days:
https://files.red-gate.com/link/Toash4XL6qVLkCBexiBOeQ
Thank you,
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools
Thanks for your post.
Just to let you know that the team are currently working on SQL Search replacing the index components which will be available in a later version, possibly V3.0.8 or the release after this.
Kind regards
Redgate Software
NOTE: updated version released since this post. Check further down the page.
Thanks for your post.
We do not have a fixed time for resolution on this yet but the development team are working on it.
For now we recommend reverting to SQL Search version 3.04
You can get it from my link below.
ftp://support.red-gate.com/patches/SQLSearch/17Nov2017/SQLSearch.exe
I hope this helps to resolve it for now.
Kind regards and have a good weekend!
Redgate Software
Thanks for your post.
As stated we currently recommend reverting to SQL Search version 3.04
You can get it from my link below.
ftp://support.red-gate.com/patches/SQLSearch/17Nov2017/SQLSearch.exe
I hope this helps to resolve it for now but please keep an eye out for the next release.
Redgate Software
I have some good news. V3.1.0.1966 is now available that fixes the problems with SQL Search returning false results or no results.
In the background, the indexing module of SQL Search has been redesigned to fix the problems reported in this forum thread.
If you wish to upgrade to SQL Search V3.1.0.1966, please use the link below to download:
ftp://support.red-gate.com/patches/SQLSearch/20Mar2018/SQLSearch_3.1.0.1966.zip
Many thanks
Eddie
Senior Product Support Engineer
Redgate Software Ltd
Email: support@red-gate.com
I just installed it, and I promise to get back here in 24h and tell about my experience.
Thanks for checking this.
It is available both from the link above and also from our Website in the link below which is http.
http://download.red-gate.com//checkforupdates/SQLSearch/SQLSearch_3.1.0.1966.exe
I hope this helps.
Best
Richard Lynch.
Redgate Software
Btw, using ssms v17.5.
The only issue is that it sometimes does not refresh the results after my search. I need to toggle on and off the "Match whole words only" checkbox in order to see the results my the search.
But the good news is that the search is back accurate, previous version was certainly dangerous. Thanks RG for the fix and for the new wildcard search functionality you brought with it.
The SQL Source Control is no longer available and the SQL Search button doesn;t work.
I've had to spend time uninstalling and reinstalling the toolbelt to get back to where i was before.
How can i install the new version of sql search without encountering this error?
I confirm glfores' issue. Start it up, indexing is fairly quick against my local database. Much slower against remote and Azure. Also seems to reindex every time the server is changed, so switching back and forth is difficult.
Then, against a remote server on which I only have permissions for a single database, the "indexing forever" issue begins. Nothing can stop it. Disconnect from the remote server. No change. Disconnect from all servers. No change. Close the Search tab. Reopen. Still "indexing."
Have to restart SSMS to get back to ground zero. Since 95% of the time I'm using this against my local development DBs, it's not a showstopper (yet), but it's definitely an issue.
As far as accuracy goes--in my initial tests, this release seems to have solved the original problem.
Thank you for this info.
We have alerted the development team to these indexing issues and they are now being worked on under bug reference number SDI-735.
We will get back to you on this as soon as it has been fixed.
Kind regards
Richard Lynch.
Redgate Software
Thanks for your post and apologies for the delay in reply.
Please find the very latest version in the link below which should get around this issue.
ftp://support.red-gate.com/patches/SQLSearch/04Apr2018/SQLSearch_3.1.3.2006.exe
Do let us know if there are still any issues.
Best
Richard Lynch.
Redgate Software
Still no "exclude comments" option for excluding commented sections in stored procedures?
Thanks for your post.
Another version has just been released today if you'd like to try it. It is available below.
ftp://support.red-gate.com/patches/SQLSearch/16Apr2018/SQLSearch.exe
Kind regards
Richard.
Redgate Software
Boom! thank you Richard - this has installed without error , and my first search has come back with results.