Liquibase Enterprise was formerly known as Datical DB.

Liquibase Enterprise v7.10 - Release Notes

Owned by Former user (Deleted)
Last updated: Nov 17, 2022 by Roderick Bowser
4 min read

Table of Contents

Software Downloads

Go to https://software.datical.com to download files. See details for the release below. 

Known Issues

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 https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/2250834093. For Azure SQL Managed Instance, see https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/2244771913.

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 is fixed in 7.11 (and higher).

Credential prompts don’t work after enabling and then disabling Runtime Credentials

If you enable and then disable Runtime Credentials for a project that has stored credentials for
dbDefs, the credentials will be cleared from the project. Running an operation (Status, Forecast, Deploy, and others.) when the project is in this state will prompt you for credentials, but the operation will fail with an authentication error. To work around this, re-enter the missing credentials using the Edit Connection dialog in the GUI for each of the effected dbDefs. 

This issue is fixed in 7.12 (and higher).

Documentation for v7.10

Documentation for the base release is available in the following forms:

Liquibase Enterprise & Business Clients (Datical DB)

Item

Path

File

Item

Path

File

Software

COMMON/Datical_DB_Software/Datical_DB_7.10.6941

Choose the Linux or Windows installation file for your system

Liquibase Enterprise Documentation

COMMON/Datical_Documentation/Datical_DB_Documentation

datical_db_docs_v7.10.pdf

Composite Installation Repository

COMMON/Datical_DB_Software/Datical_DB_7.10.6941

DaticalDbCompositeRepo-7.10.6941.zip

Liquibase Deployment Monitoring Console (DMC)

Starting with release 7.0, Liquibase includes a web-based Deployment Monitoring Console (DMC) that provides a centralized location to view a pipeline status and reporting information for all your Liquibase Business & Enterprise projects.

To get started with DMC, check out the following documentation resources:

Deployment Monitoring Console Software and Documentation

Liquibase Enterprise & Business Clients (Datical DB) and DMC Compatability

Each DMC release only works with certain releases of Liquibase Enterprise & Business Clients (Datical DB). Consult the Datical DB and Deployment Monitoring Console Compatibility Matrix to ensure compatibility.

Item

Path

File

Item

Path

File

Software

COMMON/Datical_DMC_Software/Datical_DMC_7_10_214

datical-service-unix-7_10_214-master.sh

DMC Documentation

Online @ dmc.datical.com

<N/A>

Deployment Monitoring Console Update Instructions

To upgrade from Datical Service 6.17 or earlier, see the DMC Upgrade Guide.

The process of updating the Deployment Monitoring Console from version 7.0 or later to the latest version is similar to the installation process.

  1. Go to software.datical.com, download and copy the datical-service-unix-7_10_214-master.sh file to your existing DMC server.

  2. Run the installer with the following command and enter your existing OS user as the admin user and admin group:

/home/datical> sudo bash /datical-service-unix-7_10_214-master.sh

3. Enter the directory of the previous DMC installation when prompted for an install location.

The installer will update your installation and restart affected DMC services. You can begin using the new version of the DMC immediately.

New Features

Support for Azure SQL Managed Instance

In release 7.10, Liquibase Business & Enterprise includes extended support for Azure SQL Managed Instance. Users of Azure SQL Managed Instance can now deliver high-quality database updates using Liquibase’s CI/CD workflow and authenticating in the following ways:

  • SQL Authentication

  • Active Directory Integrated Authentication

  • Active Directory Password Authentication

  • Active Directory MSI Authentication

Consider all prerequisites before connecting to Azure SQL Managed Instance from Datical DB. To get started, refer to the documentation: .

Export of CSV Files From Status Pages in DMC

From now on, if you use DMC, you can export CSV files from status pages and create reports that are not included in Datical DB. For example, you can export details of pipeline or dbdef status.

If you have filtered your status view on a specific data set, there is an option to export only the filtered content so that you don’t have to filter it again once you have the export.

Issues Addressed

Liquibase Business & Enterprise Issues

Issue ID

Description

Issue ID

Description

DAT-3443

Packager: Clarify error message when the -ignore file is non-empty (not 0 bytes).

DAT-4763

Deploy report shows success when sql for change type autoSynonymForObjects returns an error. Incorrect messaging logged in deploy report.

DAT-5391

Filenames that contain the word "cleanup" throw "No matching changesets". Packaging error when updating with -replace files.

DAT-5788

The ability to change the tracking schema to a variable in the GUI.

DAT-5825

Incorrect status when using deployLatest and when some lower versioned changesets were not deployed to dbDef.

DAT-5847

ForecastDML. When two DML scripts are added to the same changeset, then the command output shows Command Output for the second script incorrectly.

DAT-5903

Error running the deployPackager.groovy cleanup (or hammer releaseLocks): ORA-00942: table or view does not exist.

DAT-6129

UI: Add ActiveDirectoryIntegrated support in Eclipse UI.

DAT-6356

GUI: Specifying a path to the drivers isn't working.

DAT-6394

Internal rule modifyDataType fails for large Oracle tables.

Deployment Monitoring Console (DMC) Issues

Issue ID

Description

Issue ID

Description

DAT-4434

Ability to export csv files from DMC status pages (in order to be able to create additional reports that are not in the product)

DAT-5783

Duplicate rows in the DMC projects table causes the Packager error.

DAT-6128

DMC should support more than 255 characters for contexts, labels, and comments (Oracle, SQL Server, DB2).

DAT-6296

DMC vulnerability "http-options-method-enabled".
HTTP OPTIONS is disabled by default and can be enabled with the following steps:

  1. Add the setting datical.options-request-disabled=false to <DATICAL_SERVICE_INSTALL_FOLDER>/datical-service/config/application.properties file.

  2. Restart datical-proxy using the command sudo service datical-proxy restart.

  3. Restart datical-service using the command sudo service datical-service restart.

Copyright © Liquibase 2012-2022 - Proprietary and Confidential