Table of Contents
Expand | |||
---|---|---|---|
| |||
|
...
|
Software Downloads
Go to https://software.datical.com to download files. See details for the release below.
Known Issue in 7.9 Release
Active Directory Integrated Authentication option is not available in the GUI
After announcing the release of DaticalDB/Liquibase Enterprise 7.9, we discovered that GUI was missing the option to set the authentication type to Active Directory Integrated for Azure SQL Databases. Underlying functionality that relies on Active Directory Integrated authentication was confirmed to work as expected and this issue is limited to the GUI.
The following workaround can be used if you wish to use the 7.9 release to manage Azure SQL Database resources:
Configure the new DbDef for Azure SQL Database selecting Active Directory Password Authentication as described here: Creating Connections in Liquibase Enterprise and Azure SQL Database
After saving the DbDef, open the
datical.project
file in the root directory of projectUpdate the
authentication
attribute for the DbDef as shown:authentication="activeDirectoryIntegrated"
The issue is fixed in 7.10 (and higher).
Customer Notices for Upgrades
Warningnote |
---|
In recent releases Liquibase Enterprise and Liquibase Business has introduced newer versions of third party utilities to improve performance and maintain security
Please use the full install process for the desktop client GUI when upgrading from Liquibase Enterprise or Business 7.5 or earlier to Liquibase Enterprise or Business 7.89 (NOT an upgrade/update process):
|
Documentation for v7.9
Documentation for the base release is available in the following forms:
Confluence space for Liquibase Enterprise/Datical DB - Datical Product Documentation Home
PDFs for Liquibase Enterprise on software.datical.com
Confluence space for Liquibase Business - https://datical-cs.atlassian.net/wiki/spaces/LBP
Liquibase Enterprise & Business Clients (Datical DB)
Item | Path | File |
---|---|---|
Software |
|
| Choose the Linux or Windows installation file for your system. | |
Liquibase Enterprise Documentation |
|
|
Composite Installation Repository |
|
|
|
|
Liquibase Deployment Monitoring Console (DMC)
With the 7.0 release Liquibase included a new, lightweight web-based Deployment Monitoring Console (DMC) that provides status and reporting information for all of your Liquibase Business & Enterprise projects through a browser. The new DMC is a simpler replacement for Datical Service that is much easier to install, manage and use.
Expand | ||
---|---|---|
| ||
To get started with DMC check out the following documentation resources: |
Deployment Monitoring Console Software and Documentation
Info |
---|
Liquibase Enterprise & Business Clients (Datical DB) and DMC CompatabilityEach 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 |
---|---|---|
Software | COMMON/Datical_DMC_Software/Datical_DMC_7.7.197 |
|
DMC Documentation |
|
Deployment Monitoring Console Update Instructions
To upgrade from version 6.17 or earlier of Datical Service, consult the DMC Upgrade Guide
...
Expand | |||||
---|---|---|---|---|---|
| |||||
|
New Features
Support for Azure SQL DB
Liquibase Business & Enterprise have extended full support to Microsoft’s DBaaS offering Azure SQL Database. Users of Azure SQL Database can deliver high quality database updates faster and safer using Liquibase’s CICD workflow that includes:
Deploy Packager
Customizable Rules Validation
Detailed Status & Reporting
To get started, consult the documentation: Azure SQL Database Setup
Note: Microsoft’s Azure SQL Managed Instance will be supported in a future release.
Note |
---|
Impact of Updated MSSQL JDBC Driver on Previous Installations of Liquibase Business & Enterprise (Datical DB)To support Azure SQL Database, the SQL Server JDBC driver distributed by Microsoft and provided on our update site was updated to version
|
Configurable Pattern Matching for Label Assignment in Source Code Control Commit Messages
By default, comma separated string values that are surrounded by square brackets in source code control commit messages will be added as labels to changesets produced by the corresponding scripts. Users can now override the use of square brackets with a different pattern provided as a regular expression in the commitMsgLabelRegexp
property in their deployPackager.properties
file for a given project. For more information see Using the Required deployPackager.properties File.
Enable Override for the NLS_LANG
Environment Variable for Oracle Projects
The NLS_LANG
environment variable is used by SQL*Plus & Oracle databases to ensure that script contents are correctly interpreted during execution and that data values are stored appropriately in the database. The NLS_LANG
environment variable can now be set on a project by project basis so that users no longer have to set those environment variables outside of their Liquibase Enterprise operations. For more information on setting this project property. For more information see Encoding and Characters in Script Files.
New Change Set Wizard Options for Business & Enterprise Users
We have moved the options for adding SQL scripts to the Changelog to the top of the list of Change Set Wizard options for easier access.
...
We have also added three options for SQL Scripts in the Change Set Wizard.
Option Name | When to Use It |
---|---|
Execute a DML Script with sqlplus for Oracle Databases | This option indicates that the script added to the changelog should be considered for the Oracle DML Forecast feature. The DML Forecast feature will execute the script using |
Execute with edbplus for EnterpriseDB Databases | This option should be used to execute SQL scripts with the |
Execute a SQL script file using JDBC | This was formerly the “Custom SQL (External File)” option in the Changeset Wizard. This option indicates that the script should be executed using a JDBC connection instead of an external client like |
Recent Notable Changes
(Enterprise & Business 7.6) DATA_DML Package Method Creates Changesets With Oracle SQL Parser Disabled by Default
Using Oracle SQL Parser for large DML scripts can result in performance issues during Forecast and Deploy operations. Because these scripts should only include data modifications and Oracle SQL Parser is designed to provide insight into DDL operations, Oracle SQL Parser provides little to no value to DML scripts. Starting with version 7.6, Oracle SQL Parser will be disabled for scripts Packaged using the DATA_DML
package method. If you wish to re-enable Oracle SQL Parser for scripts Packaged using the DATA_DML
package method, you may do so by setting disableSqlParser=false
in the metadata.properties
for that directory or sub-directory.
For more information consult the documentation: Using the metadata.properties file
Issues Addressed
Liquibase Business & Enterprise Issues
Issue ID | Description |
---|---|
DAT-5776 | GUI: "Execute with SQLPlus" with Forecast DML doesn't forecast scripts in Resources/sql |
DAT-5502 | Create "Execute with EDB*Plus" Option in Change Set Wizard |
DAT-5340 | GUI: ChangelogSync no longer refreshes dbDef status |
DAT-5299 | Datical install shows application requires a Java Runtime Environment 1.7.0 |
DAT-5228 | UTF-8-BOM file results in Packager error "Unable to detect character encoding for script" |
DAT-5178 | Ability to specify commit label format eg. WI 999999 instead of [999999] |
DAT-5160 | Enable setting/resetting NLS_LANG environment variable for each deployment |
DAT-4809 | Warning message says resync (should be "force sync" button and "forceSync" command) |
DAT-4606 | Strip out or ignore non-recognized characters (\xa0) from scripts |
Deployment Monitoring Console (DMC) Issues
There are no DMC updates for Liquibase Business & Enterprise release 7.9.
Known Issues & Planned Deprecation of Features
Oracle Accelerator JDBC Driver
Because of a change in deployment trends and continued improvement of the performance of Datical DB, the Oracle Accelerator JDBC Driver will be removed from our driver repository and no longer supported no later than .
Known Issues with Oracle Accelerator
Issue ID | Description |
---|---|
DAT-4808 | Packaging with manifest is failing with timeout if oracle accelerator is enabled |
DAT-4375 | GUI :: Datical Accelerator connection issue |
Documentation Spaces for Older Releases
...