Debugging a Procedural Object

You can debug a procedural object after you set breakpoints.

By setting breakpoints, you can suspend and resume execution of a procedural object during debugging, which enables you to observe and evaluate the procedural object's variables and expressions.

There can be one active connection to SQL Anywhere and Sybase IQ during a debug session. Disconnect other SQL Anywhere or Sybase IQ connection profiles before debugging.

You can use the Debug view toolbar during a debug session to resume, suspend, or terminate execution of a procedural object. After you set the breakpoints, the Debug command switches the perspective to the Database Debug perspective and suspends execution at the first breakpoint.

Similar to a launch configuration, a Database Debug session remembers the SQL statement each time you want to test your object. In addition, it allows you to examine and manipulate variables and parameters and execute procedural objects one breakpoint at a time.

During debugging, 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, right-click the value in the Variables view, and choose Change Value.
Use the Referenced Tables view to examine and modify data table data and views referenced in the procedural object.

Note: You can disable the Adaptive Server Enterprise SQL debugger using trace flag 4083. The trace flag is a startup-only traceflag and has to be specified while starting up Adaptive Server Enterprise. Turning the trace flag on or off while Adaptive Server Enterprise is running does not affect the state of the debugger.

Open the procedural object and set appropriate breakpoints.
In the Source page, right-click and select Debug.
(Optional) Change parameters as necessary.
If prompted, click Yes to confirm a perspective switch to the Database Debug perspective.

Use the following controls to navigate procedural object SQL code:

Table 1. Methods of terminating or suspending procedural object execution
Icon	Name	Action
	Suspend	Suspends execution between breakpoints or before the debug operation reaches the end of the procedure.
	Terminate	Terminates execution of the procedural object.
	Disconnect	Disconnects a client debugger from a remote debug target.
	Remove All Terminated Launches	Clears all terminated debug targets.
	Resume	Resumes a suspended thread.
	Step Into	The next statement on the currently-selected line to be executed is invoked, and execution suspends at the next executable line in the procedural object. If the statement is another stored procedure, as in a nested stored procedure, that procedural object loads into the editor window, and the first statement in that stored procedure is highlighted. The statement is highlighted at each step.
	Step Over	Skips the present highlighted statement and executes the next line in the same procedural object. If execution is at the end of a procedural object, execution continues in the procedural object from which the current procedural object was called. The cursor jumps to the declaration of the procedural object and highlights its line.
	Step Return	Returns the highlight to the previous stored procedure call level. Step Return is usually used in conjunction with Step Into.

As you step through the code, examine or change the values of local variables.
In the upper right corner of the Database Debug perspective, the Variables view tracks the variables. To change the value of a variable, right-click the variable in this view, and select Change. Enter a new value for the variable and click OK.
(Optional) Navigate to a particular statement or variable, click the statement in the Outline view, or expand Parameters and click the variable.
(Optional) Execute one or more SQL statements by highlighting the code, right-clicking, and selecting Execute Selection.

Next

Examine and edit tables referenced in the object you are debugging.