Comments
Sort by recent activity
Hi Dan, Thank you for the additional details. Could you please confirm if there have been any changes to your setup. The error message you received points to a potential issue with the .NET assembly on your system. Our application requires .NET Framework version 4.7.2 or later to function correctly, which I assume is in place since there haven't been any major changes reported. Additionally, I noticed that there was an update released for SDG to version 4.6.2 yesterday. Can you confirm if this is the version you currently have installed? If not can you let me know which version you have installed? / comments
Hi Dan,Thank you for the additional details. Could you please confirm if there have been any changes to your setup. The error message you received points to a potential issue with the .NET assembly...
Hey Dan, Apologies for the issues you're experiencing with SQL Data Generator. Could you let me know which authentication method you're using to connect to SQL Server? SQL Data Generator does not natively support Multi-Factor Authentication (MFA) for SQL Server. This is because MFA typically requires interactive prompts, which are not supported by SQL Data Generator's connection mechanisms. The tool primarily supports SQL Server Authentication and Windows Authentication. Best, Hassan Product Support Engineer / comments
Hey Dan, Apologies for the issues you're experiencing with SQL Data Generator. Could you let me know which authentication method you're using to connect to SQL Server? SQL Data Generator does not ...
Hi Vaibhav, Thank you for your inquiry about SQL Compare. You need to register SQL Compare as an Azure Active Directory application, which will generate an Application ID for authentication purposes. This setup allows SQL Compare to use Active Directory Universal with MFA authentication (Azure) to connect without requiring a username and password. If you are using a version older than 14.8.0, you will need to input the Application ID manually in the connection dialog. If you are on a version 14.8.0 or later, the Application ID is no longer necessary. You can find detailed steps in Redgate's documentation here Please let me know if you have any issues. / comments
Hi Vaibhav, Thank you for your inquiry about SQL Compare. You need to register SQL Compare as an Azure Active Directory application, which will generate an Application ID for authentication purpos...
Hi Anthony, Apologies for the delay, excluding entire schemas from comparison in PostgreSQL with Flyway isn't directly supported via a filter targeting the "schema" level. While you can use filters to exclude specific object types (like tables or functions) or certain properties (like owners or privileges), excluding an entire schema itself isn’t an option currently provided in the standard filtering capabilities of Flyway Desktop for PostgreSQL: [image] [image] [image] [image] Best, Hassan Product Support Engineer / comments
Hi Anthony,Apologies for the delay, excluding entire schemas from comparison in PostgreSQL with Flyway isn't directly supported via a filter targeting the "schema" level. While you can use filters ...
Hi Anthony, Apologies for the issues you’re experiencing with Flyway Desktop. Could you please:
Share a copy of the Flyway Desktop logs?
Let me know if you’re already using a filter file to focus on the schemas relevant to your project?
If you’re not already using a filter, you’ll need to create one to define which objects Flyway should compare. You can create a filter file by following the steps outlined in the documentation for PostgreSQL filtering: PostgreSQL and MySQL Filtering Documentation. Once you’ve set up the filter: Add it to the flyway project directory and rerun. If the issue persists after applying the filter, please send over both the Log and TOML file, and we can investigate further. Best, Hassan Product Support Engineer / comments
Hi Anthony,Apologies for the issues you’re experiencing with Flyway Desktop.Could you please:
Share a copy of the Flyway Desktop logs?
Let me know if you’re already using a filter file to focus on ...
Hi Postledm and Austinjoy, The error message "ManagedIdentityCredential authentication unavailable. The requested identity has not been assigned to this resource." indicates that the managed identity being used (likely your desktop VM’s identity) has not been assigned to the Azure SQL Database. This is why the authentication fails when trying to connect from your desktop. In your case, explicitly setting the managed identity (MI) is a good approach when making requests from your desktop, especially if you're facing a conflict where the desktop VM's identity is being used instead of the Monitor server's identity. The cause is likely due to the following:
The desktop VM’s managed identity: When connecting to the Azure SQL Database from your desktop, it may be using the desktop VM’s managed identity, which doesn’t have the necessary permissions on the database. The identity is either not assigned or not properly configured on the Azure SQL Database. You
Permissions issue: The error indicates that the identity being used doesn’t have access to the database. You need to ensure that the correct identity is assigned and that it has the required permissions, such as admin account or a user with reduced permissions as mentioned here
Please let me know if you have further issues
Best, Hassan Product Support Engineer / comments
Hi Postledm and Austinjoy, The error message "ManagedIdentityCredential authentication unavailable. The requested identity has not been assigned to this resource." indicates that the managed ident...
Hi David, You mentioned, 'If I try to add it from the browser on my desktop, it fails.' Are you attempting to use the system-managed identity in this scenario? / comments
Hi David,You mentioned, 'If I try to add it from the browser on my desktop, it fails.' Are you attempting to use the system-managed identity in this scenario?
Hey David, Apologies for the delay, The problem occurs because, when accessing SQL Monitor from your desktop (an Azure virtual machine), the system is attempting to use the Managed Identity (MI) of that desktop VM rather than the MI of the Monitor server. Managed Identity authentication typically uses the identity of the environment initiating the request, leading to this issue. Let me know if this helps or if you have any other questions. Best, Hassan Product Support Engineer / comments
Hey David, Apologies for the delay, The problem occurs because, when accessing SQL Monitor from your desktop (an Azure virtual machine), the system is attempting to use the Managed Identity (MI) of...
Hi David, Sorry to hear about the trouble you're having with SQL Monitor. I’ve just sent a file request to your email. Please upload the file there, and we'll review it. / comments
Hi David,Sorry to hear about the trouble you're having with SQL Monitor. I’ve just sent a file request to your email. Please upload the file there, and we'll review it.
Hi Erich, I’m sorry to hear about the issues you’re facing with Flyway. Based on the information you provided, it looks like the problem might be due to mismatched versions of Flyway dependencies:
Flyway Enterprise Core: 9.0.0 (org.flywaydb.enterprise/flyway-core/9.0.0)
Flyway Maven Plugin: 9.0.0 (org.flywaydb.enterprise/flyway-maven-plugin/9.0.0)
MongoDB: 10.17.1 (org.flywaydb/flyway-database-mongodb/10.17.1)
It appears that while you’re using version 10.17.1 of the Flyway library for MongoDB, the other two dependencies are still on version 9. Since you mentioned that you have Java 8 installed, it’s important to note that Flyway versions 10 and above have deprecated Java 8 and now require Java 17. Best,Hassan Product Support Engineer / comments
Hi Erich, I’m sorry to hear about the issues you’re facing with Flyway. Based on the information you provided, it looks like the problem might be due to mismatched versions of Flyway dependencies:
...