Liquibase Enterprise was formerly known as Datical DB.

Datical DB runs on the following platforms and software.

Hardware Requirements

  • Processor: Intel® Core™ i5 or better, 4 CPUs or more. 
  • Memory: 4 GB - 8 GB or more. When working with large databases, 16 GB or more may be required due to high memory requirements during packaging. 
  • Disk Space: 1 GB (for Datical Client) + 2-10 GB (for files) or more

Software Requirements

Operating System

  • Windows
    • Windows 7, 8, 10
    • Windows Server 2008, 2012, 2016
  • Linux
    • CentOS 6, 7, 8
    • Red Hat Enterprise Linux 6, 7, 8
    • Note that CentOS 8 and RHEL 8 are only supported with Datical DB versions 7.16 or higher.

Software

  • Java
    • Java 8 or higher is required to install Datical DB
    • OpenJDK Version 1.8.0_222 (Java 8) is installed and used by default in version 6.10 and later.
    • OpenJDK Version 11.0.15+10 (Java 11) is installed and used by default in version 8.0 and later.
    • You can configure Datical DB to use a specific version (within the major version requirement). See Overriding Java Use
  • JDBC drivers: set up during installation
  • Source Configuration Management (SCM) 

Internet Access

You normally need internet access from the hosts where you install Datical DB. If you access the internet through a proxy server you need to configure your browser and Datical DB to use it. 

  • Browser: See browser instructions to set it up to use a proxy server. Use a browser to download the Datical DB installation package. 
  • Datical DB: See Use a Proxy Server with Datical DB. After installation you use Datical DB to set up Datical DB updates, download JDBC drivers, and install plugins for Source Code Management (SCM).

If you do not have internet access from the hosts where you want to install Datical DB, you can download files to use for installation and updates. Move them to where those hosts have network access to it. 

Database Requirements

The following databases are supported. 

DatabaseVersionsNotes
IBM DB2
IBM DB2 LUW
  • 9.7
  • 10.5
  • 11.1
  • 11.5 
Support for 11.5 was added in release 7.12 
Microsoft SQL Server
Microsoft SQL Server
  • 2012
  • 2014
  • 2016
  • 2017
  • 2019

JDBC driver supports TLS 1.0, 1.1, and 1.2

(Support for 2008 was dropped in 7.9 release)

(Support for 2017 & 2019 was added in 7.9 release)

Azure SQL DatabaseLatest Compatibility LevelAs of the 7.9 Release
Azure SQL Managed InstanceLatest Compatibility LevelAs of the 7.10 Release
SSIS


  • 2012 - SSIS projects and SSIS packages
  • 2014 - SSIS projects only
  • 2016 - SSIS projects only
Oracle
Oracle
  • 11g*
  • 12c*
  • 18c
  • 19c
Oracle 11g & 12.1c are fully supported up to and including the 7.7 release. In the 7.8 release, we updated the Oracle Instant Client & Oracle JDBC driver to newer versions that lack support for Oracle 11g & 12.1c 
Oracle on Amazon RDS
  • 12c version
    • 12.2.0.1*
  • 12c version
    • 12.1.0.2
  • 19c version
    • 19.0.0.0

Oracle on Amazon RDS has some different behaviors than on-prem Oracle. The permissions required for the Datical user are slightly different and the backup configuration is different.

*AWS will end support for 12.2.0.1 on March 31, 2022

Postgres
EDB Postgres
  • 9
  • 10
  • 11

PostgreSQL Community
  • 9
  • 10
  • 11
  • 12
  • 13
Support for 12 & 13 was added in 7.15 release
PostgreSQL on Amazon RDS
  • 9.6
  • 10
  • 11
  • 12
  • 13
Support for 12 & 13 was added in 7.17 release
PostgreSQL on Amazon Aurora
  • 9 (deprecated by AWS)
  • 10
  • 11
  • 12
  • 13
Support for 12 & 13 was added in 7.17 release

Database Setup

For a general overview of the schema or databases required for a release pipeline, see Overview of Databases Used by Liquibase Enterprise

You typically need to create the following objects:

  • REF database - Serves as the first step in any release pipeline. It is the CI deployment target when Datical DB packages SQL scripts and refactors them into changesets. 
  • Tracking database or schema - Tracks the changes deployed to each database in the pipeline. A tracking database or schema is needed for each database in the release pipeline. 
  • DMC Database - Records operations for Datical DB release pipelines. DMC (Deployment Monitoring Console) provides you a centralized location to view status and reports across Datical projects. 

For instructions on setting up Datical DB to work with your database, see the section for your database type in Configuring Databases for Liquibase Enterprise Release Pipelines.

You typically need to do the following tasks:

  • Install a database client. 
  • Create a DATICAL USER and DATICAL PACKAGING. Give them the required permissions. Datical DB operates as those users to deploy changes to the databases in the release pipeline.



Copyright © Liquibase 2012-2022 - Proprietary and Confidential