|
Client/Server
Software Benelux
Tel: +31 23 542 22 27
Embarcadero SQL Debugger
Isolate and correct faulty database logic that could
lead to expensive application downtime
Creating
optimized and accurate database code fast and efficiently is the
goal of every developer. When you are working with large amounts
of code, isolating and fixing a bug can be like finding a needle
in a haystack. Embarcadero SQL Debugger removes the guesswork from
troubleshooting database code logic errors and inefficiencies.
Embarcadero SQL Debugger allows you to step through code as it
executes, enabling you to watch database logic and quickly identify
the source of errors. As an added bonus, you can set a code profiling
option that displays the expense of each line of code as it is executed,
indicating potential performance bottlenecks in the current body
of work. And, because Embarcadero SQL Debugger provides a common
user interface for all major DBMS platforms, businesses can lower
costs and boost productivity by standardizing on a single database
administration solution.
The Embarcadero SQL Debugger is available as a licensed add-on
within DBArtisan and Rapid SQL.
Debug Procedures, Triggers, Functions*, Packages*
and Adhoc SQL Scripts
Launching
a debugging session is as easy as selecting a procedure, function,
package or trigger, and right-clicking the mouse to select Debug
from a context menu. The Embarcadero SQL Debugger automatically
determines the number, type and name of any input parameters and
presents a sizable dialog, and prompts you for each input variable
value before beginning the debug session. If a procedure or function
takes records or types as parameters, the application automatically
generates an anonymous block for debugging purposes.
*Oracle only
Step Through Code One Line at a Time
The Embarcadero SQL Debugger uses several navigational functions
to interactively walk programmers through code as it
executes on the database. You can step into nested stored
procedures to unlimited levels, as well step out of
child objects, resuming line-by-line, step debugging in the parent
object.
During a debugging session, programmers can set one or more breakpoints
in the currently executing code or in any stored object in the program
call stack. Breakpoints can be temporarily disabled or enabled without
having to add or remove them. To make you more productive, the Embarcadero
SQL Debugger remembers all breakpoints in the program and any nested
programs from one debugging session to the next. The Embarcadero
SQL Debugger also offers a profiling option that details how long
each line of code - SQL or procedural - takes to execute (in milliseconds).
In addition, the Embarcadero SQL Debugger allows you to view output*
and temp table data** throughout the debugging session.
* - All platforms
** - Sybase only
Capabilities include:
- Step Into: which executes the current instruction. If
the instruction makes a call to a stored object, the application
steps inside the nested child object.
- Step Out: which executes the remainder of the dependent
child object and resumes line-by-line, step-debugging in the parent
object.
- Step Over: which executes the current instruction without
stepping into a nested child object if the instruction makes a
call to a dependent object.
- Run to Cursor: which executes all instructions between
the pointer and the cursor and then stops.
- Go: which executes all instructions and stops only upon
program completion or when encountering a breakpoint.
- Breakpoint: which enables or disables a breakpoint at
the current instruction line. Breakpoints can be set with no condition,
a conditional expression or a skip count (stop after the breakpoint
is skipped a certain number of times).
Watch Variables, Call Stacks and Dependencies
After a debug session is initialized, programmers are presented
with four debug view windows at the bottom of the screen under the
source code: Watch, Variables, Call Stack and Dependency Tree.
- Watch Window: Programmers can specify variables to evaluate
or modify during a debug session by highlighting a variable in
the source code window and dragging it to the watch window. The
variable value can be changed during program execution by double-clicking
on it in the Watch Window. The Embarcadero SQL Debugger remembers
all watch variables between debugging sessions.
- Variables Window: The Variable window contains a list
of local variable names, types, and values for the currently executing
stored objects. It enables users to observe variable values change
as you step line-by-line through SQL code.
- Call Stack Window:The Call Stack window displays the
entire chain of nested stored objects as programmers step through
the debugging process, and can be used to display the source code
for any object in the chain, and to set breakpoints.
- Dependency Tree:The Dependency Tree window displays any
database objects that the program accesses in a hierarchical tree.
Users can double-click on an entry in the tree to display the
source code for a dependent object.
DBMS Support
Embarcadero SQL Debugger supports the following DBMS versions running
on both UNIX® and Windows NT-based servers.
- Sybase® ASE 12.0.0.3 ESD3, 12.0.0.4 & 12.5
- Microsoft® SQL Server 7.0 or above
- Oracle® 7.3.3 or above
- DB2 UDB 7.2 or above
Systems Requirements
- Windows 98, NT, 2000, or XP
- 64 MB memory
- 42 MB disk space
Home --> Products
--> Ensure --> SQL
Debugger |
|