Comments
Sort by recent activity
Hi @Faizul_Hussain This is currently a known issue with Azure Managed Instances and using Entra with MFA Could you downgrade to using this version here: https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_10.14.6.5992.exe Then also use SSMS versions 18.12.1 or 19.2 / comments
Hi @Faizul_Hussain This is currently a known issue with Azure Managed Instances and using Entra with MFACould you downgrade to using this version here: https://download.red-gate.com/checkforupdates...
Hi @Faizul_Hussain Can I ask are you using an Azure Managed Instance authentication using Entra MFA (Azure AD MFA)? / comments
Hi @Faizul_Hussain Can I ask are you using an Azure Managed Instance authentication using Entra MFA (Azure AD MFA)?
Hi @conquererbibek This would be an issue with Git and I'd advise working through some troubleshooting steps given in this forum: https://stackoverflow.com/questions/32238616/git-push-fatal-origin-does-not-appear-to-be-a-git-repository-fatal-could-n / comments
Hi @conquererbibekThis would be an issue with Git and I'd advise working through some troubleshooting steps given in this forum: https://stackoverflow.com/questions/32238616/git-push-fatal-origin-d...
Hi @shivvy I've been able to reproduce this behaviour, apologies for this inconvenience, I'm going to escalate this straight to the developers As a temporary workaround, you can modify the database connection strings if you go to the project in file explorer and edit the "sqlproj.user" file / comments
Hi @shivvy I've been able to reproduce this behaviour, apologies for this inconvenience, I'm going to escalate this straight to the developers As a temporary workaround, you can modify the database...
Hi @shivvy We've just released SQL Change Automation version 4.6.24074 which should resolve the issue with the connection dialogue in Visual Studio / comments
Hi @shivvy We've just released SQL Change Automation version 4.6.24074 which should resolve the issue with the connection dialogue in Visual Studio
Hi @haml Unfortunately, this isn't possible within the command line / comments
Hi @haml Unfortunately, this isn't possible within the command line
Hi @JeromeL, @YLarente, @JM123 I've been able to reproduce this behaviour, apologies for this inconvenience, I'm going to escalate this straight to the developers As a temporary workaround, you can modify the database connection strings if you go to the project in file explorer and edit the "sqlproj.user" file / comments
Hi @JeromeL, @YLarente, @JM123 I've been able to reproduce this behaviour, apologies for this inconvenience, I'm going to escalate this straight to the developers As a temporary workaround, you can...
Hi @JeromeL, @YLarente, @JM123 We've just released SQL Change Automation version 4.6.24074 which should resolve the issue with the connection dialogue in Visual Studio / comments
Hi @JeromeL, @YLarente, @JM123We've just released SQL Change Automation version 4.6.24074 which should resolve the issue with the connection dialogue in Visual Studio
Hi @EricLamontagne If you can hold off from upgrading to 17.9 & 17.9.1 that would be great as there's currently an issue with modifying database connections / comments
Hi @EricLamontagne If you can hold off from upgrading to 17.9 & 17.9.1 that would be great as there's currently an issue with modifying database connections
Hi @Sutrishna Unfortunately, it's not possible to create migration scripts using the Flyway CLI and you will need to use Flyway Desktop Teams or higher to generate those automatically / comments
Hi @SutrishnaUnfortunately, it's not possible to create migration scripts using the Flyway CLI and you will need to use Flyway Desktop Teams or higher to generate those automatically