Activity overview
Latest activity by Vic
Hi We have no plans for this. / comments
HiWe have no plans for this.
Error: oops The page you were looking for doesn't exist
If you see the message ‘oops, the page you were looking for doesn’t exist’ when trying to view your Redgate support tickets in the Help Center, it usually means you’re signing into your Redgate acc...
Hi Joe Giordano The tools in the TBE bundle have now all received updates so that they now work with SSMS 22.3. What caused this issue SSMS 22.3 introduced changes to internal components used by extensions. Older Versions of the tools depend on earlier version of these components. When loaded in SSMS 22.3, this mismatch causes SSMS to crash during startup or when Object Explorer in SSMS is accessed. The latest version on the tools with now work with SSMS 22.3, however they will no longer work with SSMS 22.2 and below. SSMS 21 and earlier, and Visual Studio, are unaffected. Toolbelt Essentials installer: https://download.red-gate.com/installers/SQLToolbeltEssentials/2026-02-20/SQLToolbeltEssentials.exe / comments
Official comment
Hi Joe Giordano The tools in the TBE bundle have now all received updates so that they now work with SSMS 22.3. What caused this issueSSMS 22.3 introduced changes to internal components used by ext...
SSMS 22.3 compatibility and fix
Thank you for your patience, the tools in the SQL Toolbelt Essentials bundle have now all received updates so that they now work with SSMS 22.3. What happenedSSMS 22.3 introduced changes to interna...
Hi Mathieu Souphy We are aware of this issue and a fix is in progress with our development team. We have identified the root cause of the problem and our engineers are actively working on a fix. At this time, there is no known rollback version of our tools that is compatible with SSMS 22.3. To restore a stable working environment, we currently recommend rolling back SSMS 22.3 to an earlier version of SSMS 22 where our tools function as expected. We're hoping to have a release today. / comments
Official comment
Hi Mathieu Souphy We are aware of this issue and a fix is in progress with our development team. We have identified the root cause of the problem and our engineers are actively working on a fix. At...
SSMS 22.3 compatibility and fixes
Thank you for your patience, the tools in the SQL Toolbelt Essentials bundle have now all received updates so that they now work with SSMS 22.3. What happenedSSMS 22.3 introduced changes to interna...
Hi Karsten Weldingh Thanks for bringing this to our attention. The link on SQL Prompt welcome page is now redirecting properly to the Refactoring section. / comments
Official comment
Hi Karsten Weldingh Thanks for bringing this to our attention.The link on SQL Prompt welcome page is now redirecting properly to the Refactoring section.
Hi scottie_hackleman I'm please to inform you that the latest version of SQL Prompt resolves the issue of SQL Search not returning any results. You can find the installer and the relevant release notes below: https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_11.3.3.20567.exe Release Notes [image] / comments
Hi scottie_hackleman I'm please to inform you that the latest version of SQL Prompt resolves the issue of SQL Search not returning any results. You can find the installer and the relevant release n...
Hi Adam Please can you uninstall and reinstall SSMS 22, then uninstall and reinstall SQL Search. / comments
Hi AdamPlease can you uninstall and reinstall SSMS 22, then uninstall and reinstall SQL Search.
Hi After testing, we were able to replicate the issue. Having SQL Change Automation installed will break SQL Search. This has been escalated to the developers for further investigation. If you don't use SQL Change Automation, uninstalling it should resolve the issue. If you do use SQL Change Automation, hold tight as we'retesting for a workaround while the issue is being worked on. / comments
HiAfter testing, we were able to replicate the issue. Having SQL Change Automation installed will break SQL Search. This has been escalated to the developers for further investigation. If you don't...