Page Comparison

...

• SQL Parser only applies to changes that are:
  • Packaged using the DIRECT, DDL_DIRECT, or SQLFILE method
  • Created in the ChangeSet Wizard as 'Execute a SQL script file using JDBC'/'Custom SQL (External File)'. NOTE: Changes created as 'Custom SQL' will NOT be processed by SQL Parser.
  • Created in the ChangeSet Wizard as 'Execute with SQLPlus'
• SQL Parser does not change how these scripts are ultimately executed during a Deploy operation. The following package methods all result in execution of a SQL script:
  • DIRECT packaging method
  • DDL_DIRECT packaging method
  • SQLFILE packaging method
  • changes created as 'Execute a SQL script file using JDBC'/'Custom SQL (External File)'
  • changes created as 'Execute with SQLPlus' 
• SQL Parser does not validate SQL statements. Instead, SQL Parser simply parses provided SQL scripts and models them into Datical's object model for subsequent validation with rules and forecast.
  • In the event the SQL Parser is unable to parse a statement that is included in a provided SQL script:
    • The Forecast Report will include a warning for the statement(s) that cannot be parsed. The warning will read: "WARNING - Changes in this script will not be simulated in Forecast. Custom rules will still apply"

    • SQL Parser will continue parsing the provided SQL script and attempt to parse all other statements

      Warning
      SQL Parser is unable to handle parsed changesets that are dependent on unparsed changesets in the same Forecast.

      
      

  • In the event the SQL Parser is unable to parse the provided SQL script file or otherwise encounters an error:
    • The Forecast Report will include a warning that will read: `SQL Parser could not parse sql script file <script>`
• We recommend that you do not put large DML scripts with many insert or update statements in folders that have SQL Parser enabled. 
  • See Recommendations for Working with Large DML Scripts (SQL Parser forecasting)

...