Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

From time to time certain settings need to be updated to improve Datical's deployment performance. This is especially true when you upgrade from an older version of Datical to a newer version which takes advantage of enhancements introduced in the new release.

These are some settings that are known to improve performance. 

These settings can up changed from Datical GUI or directly injected into datical.project file (notice new attributes at the end):

<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="false" multiSchema="true" dbSchemaDefinition="project" schemaSelectionStep="PAMAND5" trackingSchema="DATICAL" enableRowCount="false" limitForecastProfiling="true" deployMode="quick">

In Datical GUI, you would manipulate the above mentioned settings as follows:

  • enableRowCount="false" → Uncheck the Deployment Setting > "Collect row counts for all tables during Forecast (if needed for rules)"
  • limitForecastProfiling="true" → Check the Deployment Setting > "Limit Forecast Profiling"
  • deployMode="quick" → Check the Deployment Setting > "Full Deploy" 




  • No labels