Comments
Sort by recent activity
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
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 wit...
Support for SSMS 21 GA with SQL Prompt should be available with the next release of SQL Prompt. Once this new version is out the release notes will also be updated here: https://documentation.red-gate.com/sp/release-notes-and-other-versions / comments
Support for SSMS 21 GA with SQL Prompt should be available with the next release of SQL Prompt. Once this new version is out the release notes will also be updated here:https://documentation.red-ga...
Hi all Please can you try uninstalling SSMS 21 and SQL Prompt and then reinstall, SSMS first and then SQL Prompt, to see if that fixes the issue. https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_10.16.11.16409.exe / comments
Hi allPlease can you try uninstalling SSMS 21 and SQL Prompt and then reinstall, SSMS first and then SQL Prompt, to see if that fixes the issue.https://download.red-gate.com/checkforupdates/SQLProm...
Hi Matt Chambers This is supported via PATs, like any other headless environment (e.g. pipelines). You'll need to pipe in the --email --token to the flyway command, or use environment variables as per this documentation https://documentation.red-gate.com/flyway/flyway-pipelines/personal-access-tokens. Please can you tell me which link is the broken one and I'll get this fixed? / comments
Hi Matt Chambers This is supported via PATs, like any other headless environment (e.g. pipelines). You'll need to pipe in the --email --token to the flyway command, or use environment variables as ...
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...