Page Comparison

...

Info
If you have any issues, refer to Troubleshooting Issues with Active Directory Authentication and Azure SQL Database.

...

To create a connection with the Active Directory MSI mode in the Datical DB , select GUI, go to the Edit Connection screen. Select the following:

...

enter your hostname, port, application name, database name, instance name, and MSI Client ID.

Then define properties in your driver properties file:

Go to your Liquibase Enterprise/Datical installation directory (such as C:\Apps\DaticalDB_7.13).
Edit the file called mssql_driver.properties.
Add these two lines to your mssql_driver.properties file:
trustServerCertificate=true
hostNameInCertificate=*.azure.<domain>
(Replace <domain> with your actual domain name. For example: hostNameInCertificate=*.azure.acme.com.)
Save your changes and commit the modified properties file to source control (such as Git).

Note

The appdba:sqlcmd change type is not supported when using MSI Authentication. In Packager these :

In the GUI do not use the change set type called “Execute with sqlcmd for Microsoft SQL Server & Azure SQL Databases”. Please use the “Execute a SQL script file using JDBC” change set type with MSI Authentication instead.
In Packager do not use the change types are produced by the DIRECT package method

. Use the sqlfile package method

(such as the “sql_direct” folder). Please use the SQLFILE package method (such as the “sql” folder) with MSI Authentication instead.

Versions Compared