Comments
Sort by recent activity
Hi wsauer ReadyRoll was retired in June 2018 when it was replaced by SQL Change Automation, so there isn't a future deprecation date to share, that transition has already taken place. With your SQL Toolbelt license, you're entitled to use SQL Change Automation, which is the direct successor to ReadyRoll and carries the same core functionality forward. / comments
Hi wsauer ReadyRoll was retired in June 2018 when it was replaced by SQL Change Automation, so there isn't a future deprecation date to share, that transition has already taken place.With your SQL ...
Hi wsauer ReadyRoll 1.x effectively reached end of active development in June 2018 when we relaunched it as SQL Change Automation. No bug fixes or security patches have been issued for the ReadyRoll 1.x line since then, and it should be treated as unsupported from a security standpoint. We don't have an EOL date for SQL Change Automation which remains available to active SQL Toolbelt license holders. The current direction of travel is a migration to Flyway Enterprise, which is the successor to SQL Change Automation and the SQL Toolbelt. On the Visual Studio extension front, the current SCA extension supports VS 2022 and VS 2025/2026, but legacy ReadyRoll 1.x and SCA 3 have no guaranteed compatibility with those versions. / comments
Official comment
Hi wsauer ReadyRoll 1.x effectively reached end of active development in June 2018 when we relaunched it as SQL Change Automation. No bug fixes or security patches have been issued for the ReadyRol...
Hi michael sim Please can you follow the steps in this article: SQL Prompt missing from toolbar after installation / comments
Hi michael sim Please can you follow the steps in this article:SQL Prompt missing from toolbar after installation
Hi Erik Kisant There was a permissions issue which we've fixed. You should be able to log in and see your licenses now. Sorry for the inconvenience. / comments
Official comment
Hi Erik Kisant There was a permissions issue which we've fixed. You should be able to log in and see your licenses now.Sorry for the inconvenience.
Heino Zunzer the fix applies specifically to SQL Prompt, as it was the only tool affected. Curtis, the correct sequence is to uninstall your Redgate tools, upgrade SSMS, and then reinstall the tools. This is the recommended workflow whenever upgrading SSMS. / comments
Heino Zunzer the fix applies specifically to SQL Prompt, as it was the only tool affected.Curtis, the correct sequence is to uninstall your Redgate tools, upgrade SSMS, and then reinstall the tool...
Thank you for your patience while we investigated this. I'm pleased to let you know that we’ve released a new version of SQL Prompt that includes a fix for this issue. You can now update to the latest version of SSMS, and it will be fully compatible with this new SQL Prompt release: https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_11.3.8.22342.exe / comments
Official comment
Thank you for your patience while we investigated this.I'm pleased to let you know that we’ve released a new version of SQL Prompt that includes a fix for this issue. You can now update to the late...
Hi B That's because you don't have a trial license assigned to your account. I'll create one for you and reach out in a support ticket. / comments
Hi BThat's because you don't have a trial license assigned to your account.I'll create one for you and reach out in a support ticket.
Hi B Do you have a trial license? Are you following the steps in this article? How to activate using offline permits / comments
Hi BDo you have a trial license?Are you following the steps in this article?How to activate using offline permits
Hi We have no plans for this. / comments
HiWe have no plans for this.
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...