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.
- enableRowCount=”false” or "approximate" → /wiki/spaces/DDD/pages/24707471
- For Datical DB versions 5.6 or lower, set it to "false" to completely disable it
- For Datical DB versions 5.7 or higher, set it to the new "approximate" option
- limitForecastProfiling=”true” → For more information on this topic: /wiki/spaces/DDD/pages/24707448
- deployMode=”quick” → For more information on this topic: /wiki/spaces/DDD/pages/523272429
- Stored Logic Validity Check="limited" → The "limited" option is only available in Datical DB 5.3 or higher: /wiki/spaces/DDD/pages/491290653
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"
- For Oracle/SQL Server/DB2, change the stored logic validity check from "local" (the default) to the new "limited" value.
- Note that the "limited" option is only available with Datical version 5.3 or higher. (If you are using version 5.2 or lower, you could set it to "disabled" but use caution and only do that if you do not need the stored logic validity check at all.)
- In datical.project file, this is represented as storedLogicValidityCheck="limited"
<dbproject:Projectxmi: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"storedLogicValidityCheck="limited"runtimeCredentials="false"multiSchema="true"dbSchemaDefinition="project"schemaSelectionStep="PAMAND5"trackingSchema="DATICAL"enableRowCount="false"limitForecastProfiling="true"deployMode="quick">
- In Datical GUI, make this change in Deployment Settings > Stored Logic Validity Check > select "Limited"
Related articles