Powered by Zoomin Software. For more details please contactZoomin

DataDirect OpenAccess SDK Help

Query execution analysis

  • Last Updated: May 12, 2026
  • 1 minute read
    • OpenAccess SDK
    • Version 8.1
    • Documentation

You can configure the OpenAccess SDK SQL engine to log query execution plans to a file by using the ServiceIPSqlEngineVerboseLogLevel attribute, which can be set for different levels of logging. The output is written to a file with the name ServiceName_pid_seq.number-sqlverbose.log in the directory specified by ServiceDebugLogPath. Refer to the OpenAccess SDK Administrator’s Guide for details.

describes the type of output generated for each log level setting. You can configure the SQL engine to log both the details of the query that is being executed and how the IP is interacting with the SQL engine. Following the table are examples of the information that is logged according to the log level settings.

Verbose logging options

Option Description
SQL Engine Plan Reports the query plan with the following details:
  • Query string
  • Parsed Query—Query Parse tree
  • Validated Query—A query parse tree where each table and column reference is identified by table number and column number
  • Join Order
  • Execution Plan and Query Index condition
  • Query Result Specification—Column name, data type
  • Block Join expression details
  • SQL Engine Calls by IP Reports the Condition list returned by the following options:
  • dam_getOptimalIndexAndConditions
  • dam_getRestrictionList
  • dam_getSetOfConditionLists
  • dam_getSetOfConditionListsEx
  • damex_getSetOfConditionLists
  • This option also reports how condition lists are modified to handle block join mode.
    Reports on how the IP is building results using the following options:
  • dam_allocRow
  • dam_addValToRow
  • dam_isTargetRow
  • dam_addRowToTable
  • dam_allocRowSet
  • dam_addRowToRowSet
  • dam_addJoinRowSet
  • TitleResults for “How to create a CRG?”Also Available inAlert