...
- In the desktop client/Eclipse GUI, set it on the REF dbDef step. See "CLPPLus Timeout (seconds)" for DB2, "SQL*Plus Timeout (seconds)" for Oracle, "EDB*Plus Timeout (seconds)" for Postgres, and "SQLCMD Timeout (seconds)" for SQL Server here → Configuring Step Settings (DbDefs)
- Set it using the hammer CLI command (example: "hammer set scriptExecutionTimeout REF 600"). See scriptExecutionTimeout here → CLI Commands#set
- If you use the optional project creator script, see scriptExecutionTimeout here → Creating a Datical Project Using the Project Creation Script (project_creator.groovy)
13. If you run deployPackager on Windows clients or Windows agents, please consider upgrading to Datical version 6.8 or higher. We made performance improvements for forecast on Windows in Datical version 6.8 (or higher). Performance improvements for forecast can also improve performance time for deployPackager, since deployPackager does run forecast. This performance improvement can be noticeable compared to older versions of Datical when you run hammer commands on a Windows machine or when you run the Datical desktop client/Eclipse GUI on a Windows machine. (This code change is not relevant if you run Datical on a Linux box.)14. If you don't need to use the Forecast DML project setting, disable it.
...
- In the desktop client/Eclipse GUI, go to the Settings tab. Expand the Deployment Settings section. Disable the "Forecast Data Modification Changes (DML)" checkbox.
- Disable it using the hammer CLI command: "hammer set forecastDML false"
- Recommendations for Working with Large DML Scripts
14. Upgrade to a current version of Datical:
- There were performance improvements 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 in Datical DB version 6.12 (and higher).
- There were performance improvements for several operations in Datical DB version 6.14 (and higher).
- From the 6.14 Release Notes - Areas where you may notice 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
- Change Log Sync
- From the 6.14 Release Notes - Areas where you may notice improvements:
15. Although not specifically about packager, this link includes ways to improve Deploy performance:
...