...
- There were performance improvements during the forecast stage for those who run deployPackager on Windows clients or Windows agents in Datical DB version 6.8 (and higher).
- There were performance improvements for those who use the Stored Logic Validity Check project setting in Datical DB version 6.12 (and higher).
- There were performance improvements for several operations in Datical DB version 6.14 (and higher). Areas where you may notice performance improvements:
- Status/Pipeline Status operations in the Datical DB GUI
- 'status' & 'statusDetails' commands in the CLI
- Complex operations which run status implicitly (CLI & GUI) - All types of 'deploy' operations, All types of 'rollback' operations, Deploy Packager, Convert SQL, and Change Log Sync
- There were improvements for what SQL Parser for Oracle can model in Datical DB version 6.15 (and higher).
- There were performance improvements specifically for multi-database/multi-catalog configurations of SQL Server projects in Datical DB version 6.16 (and higher).
- There is a fix for the DATAPUMP API Oracle backup and restore in Datical DB version 6.16 (and higher) to better handle running multiple packager jobs concurrently.
- There is a new cleanup command for packager in Datical DB versions 7.3 and higher. The cleanup command can be run after any time that you might need to manually interrupt a packager job midway. The cleanup command is to unblock subsequent packager jobs after a manual interruption.
This is the command:
- /home/datical/<MyBlockedProject>/hammer groovy deployPackager.groovy pipeline=mypipeline cleanup
The cleanup command should only be used after a packager job was interrupted. It will do these three things:
Release the lock on the DATABASECHANGELOGLOCK table (all database platforms).
Release the lock on the DATICAL_SPERRORLOG table (only relevant for Oracle). This table is used to capture error messages for reporting purposes during the execution of
sqlplusscripts.Restore REF DB to a working configuration.
For more information check out the this documentation page:
Deploy Packager DocumentationSee this page for more details: How To: Use ReleaseLocks Command and Packager with Cleanup Option15. Although not specifically about packager, it may also be useful to check the items on these pages that may improve Deploy performance:
...