Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Upgrading to a newer version of Datical may also be helpful (see item 6 7 below).


These are some settings that are known to improve deploy performance:

...

3.  deployMode=”quick” → For more information on this topic: "Quick Deploy" Deployment Mode

4.  Stored Logic Validity CheckstoredLogicValidityCheck="limited" → The "limited" option is only available in recommended for Datical DB 5.3 or higher: Configuring Project Settings

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

6.  autoGenSQL=false → Disabling the Automatically Generate SQL setting can improve performance if you don't need itConfiguring Project Settings


These 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 datical.project file:

Code Block
languagexml
linenumberstrue
<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="falsetrue" multiSchema="true" dbSchemaDefinition="project" schemaSelectionStep="PAMAND5" trackingSchema="DATICAL" storedLogicValidityCheck="limited" enableRowCount="approximate" limitForecastProfiling="true" deployMode="quick">

...

  • enableRowCount="approximate" → Select approximate for the Deployment Setting > "Collect row counts for all tables during Forecast (if needed for rules)"
  • limitForecastProfiling="true" → Check the Deployment Setting > "Limit Forecast Profiling"
  • autoGenSQL=false → Uncheck the Deployment Setting > "Automatically generate SQL for Forecast, Deploy, and Rollback" 
  • deployMode="quick" → Check the Deployment Setting > "Full Deploy" 
    • In Datical GUI, make this change in Deployment Settings >
    • forecastDML=false →  Uncheck the Deployment Setting > "Forecast DAta Modification Changes (DML)" 
    • storedLogicValidityCheck="limited"  → Select limited for the Deployment Setting > "Stored Logic Validity Check > select "Limited"
    • Image Modified


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

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


67.  Upgrade to a current version of Datical:

...