Opening a Debugging Session

Go Up to Using the IDERA SQL Debugger

When you start a debugging session, the IDERA SQL Debugger interface opens. For details, see IDERA SQL Debugger Interface.

If the target script requires input parameters, a dialog box prompts you for the necessary input parameters before displaying the target code in the SQL Editor window. When the target script is displayed in the SQL Editor window, you can begin debugging. For details, see Debugging an SQL Script with IDERA SQL Debugger

Note: IDERA SQL Debugger for IBM DB2 for Linux, Unix, and Windows, IDERA SQL Debugger for Sybase, and IDERA SQL Debugger for Microsoft only let you debug the SQL script of procedures or triggers.

To debug an object, do the following:

1. In the Navigator/Explorer, click the object node.

   The objects are displayed.

2. Right-click the target object, and select Open.

   The Object Editor opens.

   OR

   Right-click the target object and select Extract.

   The DDL Editor opens, displaying the code of the target object.

3. On the toolbar, click Debug.

   OR

   In the DDL Editor window, right-click, and then click Debug.

   If the script requests input parameters, a dialog box prompts for parameter values. If the script does not require input parameters, the script is displayed in the DDL Editor window for you to begin debugging. For details, see Debugging an SQL Script with IDERA SQL Debugger.

   Note: You cannot use the IDERA SQL Debugger until it has fully initialized.

4. In the dialog box, specify the appropriate parameter values, and then click OK or Continue.

   The script opens in the DDL Editor window.

   Note: If the script requires Sybase ASE or Oracle types (tables, records, or Booleans) as input parameters, the IDERA SQL Debugger generates an anonymous block.