From time to time certain settings need to be updated to improve Datical's deployment performance (see items 1 through 6 below).

You could increase

Recommendations to improve Deploy performance

• Optimize your Project Settings by disabling features you don't use or by narrowing the scope of the features you do use.
• Increase the amount of RAM used by Datical

...

• .

...

• Upgrade to a newer version of

...

• Liquibase Enterprise/Datical.

Project Settings that improve deploy performance

Check your values of these Project Settings

1.  enableRowCount=”false” ”disabled” or "approximate" → Settings for Collecting Row Counts

...

4.  storedLogicValidityCheck="disabled" or "limited" or "local": → Limited or Disabled will have faster performance than Local or Global

• Please see the notes in these pages:
  
  • Stored Logic Validity Check details
  • Project Settings
• Performance recommendations:
  • If you do not review or use the information in the Stored Logic Validity Check section of your deploy reports, then set storedLogicValidityCheck="disabled" to avoid possible performance slow down for a feature you aren't actively using.
  • If you review and use the Stored Logic Validity Check information in your deploy reports
  ,
  • but you do not use the storedLogicValidityAction=FAIL option, then
  set 
  • we recommend setting storedLogicValidityCheck="limited".
  • If you review and use the Stored Logic Validity Check information in your deploy reports and you also have enabled the storedLogicValidityAction=FAIL option, then
  set 
  • we recommend setting storedLogicValidityCheck="local". (This is the default setting.)
  • Although storedLogicValidityCheck="global" is an available setting and is the most comprehensive, if performance timing is an important consideration then it may be better to use a smaller scope such as "local" or "limited".
• Please see the notes in the "Stored Logic Validity Check" heading on this page: Configuring Project Settings
  

5.  forecastDML=false → Disabling Forecast DML can improve performance if you don't need to forecast DML: Configuring Project Settings

6.  autoGenSQL=false → Disabling the Automatically Generate SQL setting can improve performance if you don't need it: Configuring Project SettingsThese settings can up changed from Datical GUI, or by using hammer set commands in the CLI, or by using the optional project_creator script.  Notice the attributes near the end of this excerpt from the

How the values look in datical.project file

...

Code Block
language xml linenumbers true
<dbproject:Project xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dbproject="http://datical.com/db/project/1.0" name="dpe-datical-paymentmanager" storedLogicExternal="true" deployThreshold="stopOnError" runtimeCredentials="true" multiSchema="true" dbSchemaDefinition="project" schemaSelectionStep="PAMAND5" trackingSchema="DATICAL" storedLogicValidityCheck="limited" enableRowCount="approximatedisabled" limitForecastProfiling="true" deployMode="quick" autoGenSQL="false" forecastDML="false">

How to Change the Project Settings

There are more details about each setting option on the Configuring Project Settings page.   You can change them using the method you prefer:

GUI

In the Datical desktop client/Eclipse GUI, you would set the above mentioned settings Configuring Project Settings:

...

• Image Removed

...

open your project, go to the Settings tab, and expand open the Deployment Settings section.  Here is an example of what the settings would look like in the GUI when optimizing for performance:

Image Added

Command Line

In the CLI, you can set those same items using "hammer set" commands for enableRowCount, limitForecastProfiling, deployMode, invalidsCheck, and autoGenSQL.  Please see the set command details here: CLI Commands#set

Project Creator

If you use the optional project_creator script, you can set these settings when initially creating the project.  Please see the instructions here: Creating a Datical Project Using the Project Creation Script (project_creator.groovy)7. 

Increase the amount of RAM used by Datical

The default is -Xmx2048m.  You can increase it to -Xmx4096m or -Xmx8192m.

Please see the instructions on this page: Increase the amount of RAM used by Datical DB8.  Upgrade to a current version of Datical:Liquibase Enterprise

Upgrade to a newer version of Liquibase Enterprise/Datical DB

• There were performance improvements to forecast for those who run forecast/deploy on Windows clients or Windows agents use the Stored Logic Validity Check project setting in Datical DB version 6.8 12 (and higher).
• There were performance improvements for those who use the Stored Logic Validity Check project setting Status, statusDetails, and Pipeline Status in Datical DB version 6.12 14 (and higher). This also improved operations which run status implicitly such as deploy, rollback, deployPackager, convert SQL and changeLogSync.  
• There were performance improvements for several operations in Datical DB version 6.14 memory utilization of SQL scripts that produce a high-volume output in 7.11 (and higher).
• There were improvements for SQL Parser for Oracle in version 7.12 (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 Limited Forecast in version 7.13 (and higher):
  • Limited Forecast will only profile tables impacted by the changesets to be forecasted or deployed
  • Limited Forecast will only profile the schema impacted by the changesets to be forecasted or deployed in multi-schema projects
• Significant performance improvements for Forecast profiling in version 7.14 (and higher):
  • Faster forecasting of Views and Materialized Views
  • Faster profiling for tables, columns, and views in multi-schema projects
  • Use multiple connections (maximum of 10 connections) to profile schemas simultaneously in Oracle multi-schema projects.  Note that with 7.14 (and higher) in Oracle projects with multiple schemas, you may notice higher CPU utilization due to multiple connections being used for Oracle forecast profiling.

There are other performance improvement suggestions on these pages:

...