...
| Item | Path | File |
|---|---|---|
| Software | COMMON/Datical_DB_Software/Datical_DB_7.0.XXXX | Choose the Linux or Windows installation file for your system. |
| Datical DB Documentation | COMMON/Datical_Documentation/Datical_DB_Documentation | datical_db_docs_v7.0.pdf |
| Composite Installation Repository | COMMON/Datical_DB_Software/Datical_DB_7.0 | DaticalDbCompositeRepo- |
Datical Deployment Monitoring Console (DMC)
| Item | Path | File |
|---|---|---|
| Software | COMMON/Datical_DMC_Software/ | Choose the Linux or Windows installation file for your system. |
| Datical DB Documentation | COMMON/Datical_Documentation/Datical_DB_Documentation | datical_db_docs_v7.0.pdf |
Documentation Spaces for Older Releases
See DDD in the Releases with Doc Spaces section for a list of spaces available for older releases (prior to 6.7).
New Features
Deployment Monitoring Console (DMC)
With the 7.0 release Datical is offering a new, lightweight web-based Deployment Monitoring Console (DMC) that provides status and reporting information for all of your Datical projects through a browser. The new DMC is a simpler replacement for Datical Service that is much easier to install, manage and use.
Simplified Installation, Configuration and Upgrade
The new Deployment Monitoring Console was built to get you up and running fast. Hardware requirements have been greatly simplified to reduce the time it takes to requisition a suitable system and reduce the overall operational costs of the solution. The new installer workflow is simpler and more intuitive. Upgrading to a new version is as easy as running the new installer on the system where the previous version is installed.
Centralized, Controlled Access to Database Deployment Information
The new DMC still uses Keylocak to manage user authentication and authorization. This allows you to integrate the DMC with your existing LDAP solution in order to simplify user management and control what data individual users have access to.
Reports and Details for All of Your Projects, Pipelines and Databases
Issues Addressed
| Issue ID | Description | |
|---|---|---|
| DAT-3835Incorrect Packager log message "Found 1 TYPE statements in the SQL Script" when COMMENT contains "TYPE4302 | Update Postgres Setup instructions to address RDS issue with "REASSIGN OWNED BY" | |
| DAT-3677Packager: Provide Better Mechanism to Drop Stored Logic4120 | Custom Forecast Rules run 2x for each changeset. | |
| DAT-3667DDB_USER and DDB_PASS environment variables do not work with "hammer groovy database_backup_restore.groovy4079 | Forecast Report is misleading for changes packaged using SQL_DIRECT | |
| DAT-2404 | Example scripts for Oracle Roles and Permissions should not use "$DaticalUser" | |
| DAT-3272 | TFS: Packager fails after a drop procedure or rename or revert procedure is attempted | |
| DAT-2729 | Datical Eclipse GUI: missing data_dml option when creating Manifest file with the Datical DB GUI Manifest wizard | |
| DAT-2608 | Hammer forecast or deploy output shows "unable to determine pipeline" when --pipeline is not used3619 | Property substitution fails when labels values are used (Improved logging and recommendations to avoid this scenario) |
Known Issues
Checksum Errors when Performing Status on Deployed AddUniqueConstraints Changes
...