To make the Active Directory Integrated connection from DaticalDB, you need to have two files in C:\Windows\System32 - adal.dll and mssql-jdbc_auth-<version>.<arch>.dll.

1. The adal.ddl file needs to be added to C:\Windows\System32 in the Windows registry if you receive the error message "Unable to load adalsql.dll".

2. The mssql-jdbc_auth-<version>.<arch>.dll file needs to be added to C:\Windows\System32 in the Windows registry if you receive the error message "Login failed to authenticate the user in Active Directory (Authentication=ActiveDirectoryIntegrated)".

If you use Azure SQL Database, refer to Troubleshooting Issues with Active Directory Authentication and Azure SQL Database. For Azure SQL Managed Instance, see Troubleshooting Issues with Active Directory Authentication and Azure Managed Instance.

Baseline changelog cannot be deployed using release 7.10 (Azure SQL Managed Instance only).

We discovered that DaticalDB fails to deploy a baseline generated snapshot. The reason is that Azure SQL Managed Instance automatically manages XTP filegroups and files for databases containing In-Memory OLTP objects. It means that the XTP filegroup exists on Azure SQL Managed Database right after creation and the attempted deployment fails because it already exists. For more information, see Key differences between SQL Server on-premises and SQL Managed Instance.

The following workaround can be applied if you want to use release 7.10 to manage Azure SQL Managed Instance resources:

Manually remove XTP filegroup changeset from your changelog.xml file.

The issue will be addressed in our next release.

We discovered that switching to runtime credentials on the Project Settings page doesn’t work as expected.

You will not be able to run commands using GUI if DbDef does not have a password in the datical.project file, even when you enter the password in the password dialog box. This issue will be fixed in the next release (7.11).