Versions Compared

Old Version 13

changes.mady.by.user Amy Smith

Saved on

compared with

New Version Current

changes.mady.by.user Amber Williams

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Software Downloads

Go to https://download.liquibase.com/ to download files.

...

Tip

Added MSSQL Ephemeral Database Support

For Microsoft SQL Server databases, a backup restore method is available that allows teams to create a temporary, or ephemeral, Ref DB for packaging changes. A copy is created The packaging operation creates a copy of the first database in a pipeline during the packaging operation. Scripts eligible for packaging are applied apply to the copied database, and Enterprise destroys the copy is destroyed at the end of the packaging operation.

See Configure Deployment Packager to Use a SQL Server Ephemeral Database

Associated Tickets: DAT-17547

Tip

Added PostgreSQL Ephemeral Database Support

For PostgreSQL databases, a backup restore method is available that allows teams to create a temporary, or ephemeral, Ref DB for packaging changes. A copy is created The packaging operation creates a copy of the first database in a pipeline during the packaging operation. Scripts eligible for packaging are applied apply to the copied database, and Enterprise destroys the copy is destroyed at the end of the packaging operation.

See Configure Deployment Packager to Use a PostgreSQL Ephemeral Database

Associated Tickets: DAT-18447

...

Issue ID

Description

DAT-15634

DAT-17660

Added a new property internalRules.disabledDefaultRules for to the daticaldb.properties file which provides the ability to turn off Package and Forecast Rules for ModifyDataType and other internal rules.

See How To: Turn off internal rules for CreateIndexType, CreateTableType, and ModifyDataType for additional details.

DAT-17547

Added MSSQL ephemeral database support. See Configure Deployment Packager to Use a SQL Server Ephemeral Database

DAT-18096

Fixed an issue with the CLI showing an old license even though new license has been installed when a newly installed license is available on the server. Licenses Any new license installation will now replace licenses with 30 days or less remaining will now be replaced by any new license installation. See https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/edit/896566463?draftId=901611521&draftShareId=82e7539c-fd9d-410b-bd18-c5c77d7bc30f&. (update link once published). See Install and Manage Licenses

DAT-18447

Added PostgreSQL ephemeral database support. See Configure Deployment Packager to Use a PostgreSQL Ephemeral Database

DAT-18874

Fixed an issue with the MSSQL Integrated Security dlls shipped with Liquibase. The correct version is now included with the install and is version mssql-jdbc_auth-12.4.0.x64.dll (or mssql-jdbc_auth-12.4.0.x86.dll for 32-bit machines.) See Setting up Integrated Security for Active Directory for instructions on installing the dll.

DAT-18905

Added support for sqlcmd version 18 to be used as the native executor for SQL Server deployments. See Installing SQL Server Clients

DAT-18914

Addressed an issue with Oracle Ephemeral Packaging with runtime credential support. For customers using Oracle Ephemeral Packaging and runtime credentials with Liquibase Enterprise versions 8.6 or 8.7, please contact Liquibase Support for a custom script to address this issue.

SqlParser Issues Addressed

...

Issue ID

Description

DAT-2452

Added instructions for migrating from Demo Mode to Production Mode. See https://dmc.datical.com/install/demo-mode/demo-to-prod.htm

DAT-17843

Certified DMC usage with AlmaLinux 9.

DAT-18536

Corrected an issue with sync operations for deleted pipelines where Packager operations had previously run on the deleted pipeline.

Error addressed was: ERROR: update or delete on table "dprj_environment" violates foreign key constraint "fk_dprj_packager_env_id" on table "dprj_deploy_packager"

This fix does not require a DMC update , but rather an update to the GUI or CLI to Liquibase Enterprise version 8.8.

...

...

Item

Path

File

Software

Datical_DB_Software/Datical_DB_8.8.XXX425

Choose the Linux or Windows installation file for your system

Composite Installation Repository

Datical_DB_Software/Datical_DB_8.8.XXX425

DaticalDBCompositeRepo-8.8.XXX425.zip

Liquibase Enterprise Deployment Monitoring Console (DMC)

Item

Path

File

Software

Datical_DMC_Software/Datical_DMC_8.8.XXX452

datical-service-unix-8.8.XXX452-master.sh

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

...

Each DMC release only works with certain releases of Liquibase Enterprise Desktop. Consult To ensure compatibility, consult the Deployment Monitoring Console Compatibility Matrix to ensure compatibility.

 

Expand
titleGetting Started with the Deployment Monitoring Console

DMC Update Instructions

The process of updating Updating the Deployment Monitoring Console to the latest version is similar to the installation process.

Expand
titleExpand for DMC update instructions

  1. Go to https://download.liquibase.com/ , download, and copy the datical-service-unix-<version>-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:

Code Block
/home/datical> sudo bash /datical-service-unix-<version>-master.sh

  1. 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.

Info

If you have manually changed the java Java version used by DMC, you will need to restore DMC’s default version of Java (11.0.8) before any time that you upgrade DMC. Move or copy Java 11.0.8 from the /opt/datical/old_jre directory back to the /opt/datical/jre directory prior to before starting your DMC upgrade. DMC expects Java version 11.0.8 to be in the /opt/datical/jre directory for the DMC upgrade process to be successful. After completing your DMC upgrade is complete, you can change to a different 11.x java version again. For more information, see How to Change the Java version for DMC. This link is especially important vital if you are using v7.18 or later.

...