Oracle SQL*Plus script developers without an IDE like Toad are left to debug their scripts by using echo commands or output statements, then viewing the output during code review. Trial and error may eventually lead to the “ah ha” moment when the developer would see what went wrong, but there is a better way.

The Script Debugger, is available for users who have purchased the Debugger. It allows Toad users to debug their SQL*Plus scripts the same way PL/SQL developers have been debugging stored procedures for years.

Located under the Database Menu, Script Debugger allows users to run debug sessions against their SQL (and SQL*Plus) scripts. The Script Debugger has a powerful editor, navigator panel (just like Toad’s PL/SQL Debugger), debugger engine and results panel and allows multiple files to be open simultaneously via a multi-tabbed interface. The Script Debugger tab shows system and user variables.

The Script Debugger represents a quantum leap forward, as developers are now able to execute code one line at a time and watch variables along the way. There is no need to place special debug output statements within the code (don’t forget to remove these when you are ready to move your code to production) to see exactly what is happening during code execution. The debugger allows the execution to pause and variable values may be “watched.”