...
8. For Oracle/SQL Server/DB2, change the Stored Logic Validity Check from "local" (the default) to the new "limited" value. Using "limited" will be faster than using "local" or "global".
- The "limited" option is only available with Datical DB versions 5.3 or higher.
- For Oracle, we recommend running Datial Datical DB 6.12 or higher due to a performance improvement with the "limited" option for Oracle only.In datical.project file, this is represented as storedLogicValidityCheck="limited".
- If you are using the "limited", "local", or "global" setting and you package multiple scripts in the same packaging run in the ddl folder (or with the convert packaging method), we recommend running Datical DB 6.12 or higher because the stored logic validity check will no longer be repeated redundantly for each script.
There are different ways you can set the stored logic validity check level, use the method you prefer:
- In the desktop client/Eclipse GUI, set it to limited. See Stored Logic Validity Check here → Configuring Project Settings
- Set it using the hammer CLI command (example: "hammer set invalidsCheck limited"). See invalidsCheck here → CLI Commands#set
- If you use the optional project creator script, see invalidsCheck here → Creating a Datical Project Using the Project Creation Script (project_creator.groovy)
- In the datical.project file, this is represented as storedLogicValidityCheck="limited".
9. Packaging ddl scripts from the sql_direct folder (packageMethod=direct) is typically faster than from the ddl folder (packageMethod=convert).
...