Versions Compared

Key

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

...

8.  For Oracle/SQL Server/DB2, change the Stored Logic Validity Check from to "local" (the default) to the new or "limited" value.  Using "limited" will be faster than using "local" or "global".

...

or "disabled", depending on which features you actively use:

  • If you do not review or use the information in the Stored Logic Validity Check section of your deploy reports, then set storedLogicValidityCheck="disabled".
  • 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 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 storedLogicValidityCheck="local".
  • Although storedLogicValidityCheck="global" is an available setting and is the most comprehensive, if performance timing is important 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

There are different ways you can set the stored logic validity check level, use the method you prefer to set the value:


9.  Packaging ddl scripts from the sql_direct folder (packageMethod=direct) is typically faster than from the ddl folder (packageMethod=convert).  You could also opt to set packageMethod=direct for your ddl folder.

...