...
- Caveat: If you are not using SQL Parser, then only sqlrules would apply in sql_direct folder. (Other types of rules and forecast modeling do NOT apply in the sql_direct folder if you are not using SQL Parser for Oracle.)
- If you are using Oracle with Datical DB 65.8 9 or higher you could consider using SQL Parser for Oracle to add forecast modeling and forecast rules to data_dml folder (packageMethod=data_dml) and sql_direct folder (packageMethod=direct).
- Note that there were important improvements to the SQL Parser for Oracle in Datical DB 6.15.
- Please see this page → Using SQL Parser
10. Having the build agent and the database in close proximity can help performance.
...
- 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 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 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 - All types of 'deploy' operationsAll , All types of 'rollback' operations
- Deploy Packager
- Convert SQL Change Log Sync, Deploy Packager, Convert SQL, and Change Log Sync
15. Although not specifically about packager, this link includes ways to improve Deploy performance:
...