Database Debug offers a complete set of views for debugging the procedural objects you have created. Breakpoints are set when you double-click on the left vertical ruler in the SQL Editor or by right-clicking on the marker and selecting Toggle Breakpoint. If the line is not appropriate for a breakpoint, the marker (a blue dot) is adjusted to the next appropriate line in the code. You can remove breakpoints by double-clicking or right-clicking on the marker and selecting Toggle Breakpoint.
After you have set the breakpoints, you can begin debugging via the SQL Editor context menu Debug, which automatically switches to the Database Debug perspective and suspends the execution at the first breakpoint.
In the Debug view, with the cursor at a breakpoint, use the appropriate toolbar buttons to step into or over a line of code.
Use the Variables view to track the variables in the expressions that the debugger has evaluated.
To change the value of a variable, double-click its name in the Variables view. The Set Value dialog appears. Enter a new value for the variable and click OK.
The Breakpoint view shows the line where the breakpoints are set for any type of procedural object and lets the user remove, disable, and enable existing breakpoints.
The ASA Trigger Rows view displays the rows that have errors when debugging an ASA trigger.
External Client view is used to attach to an external database client session via the isql command tool and debug it using the SQL Debugger.
Global Variables view displays all the system global variables in read-only format, for use when debugging ASA procedural objects.
SQL Results view allows you to view the run status, database server messages, and result sets, and save the result sets or results history into different file formats.
The Debug view displays the execution stack. You can use the Debug view toolbar to resume, suspend, or terminate execution of a procedural object during a debug session.
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com