Learn more about Toad for SQL Server
at Quest.com

Find solutions and downloads at the
Toad for SQL Server Support Portal

< To bookmark a page, right-click the Page Title and select Add to Favorites / Bookmark This Page

Toad for SQL Server 5.7

You are here: Edit SQL > Debug SQL > Collect and Replay Debug Traces

Collect and Replay Debug Traces

The debug trace feature collects a complete trace of everything you do when debugging stored procedure so that you can play it back later. You can then replay the trace forwards and backwards to evaluate the execution. The replay does not affect the server; it is only a local replay.

The debug trace collects the following:

Local variables and arguments. Global variables are not collected by default, but can be enabled in the options.
Step information and callstacks.
Scripts of all involved code. This means that when you replay a trace you will see the script in the editor as it looked when the trace was created regardless of whether the object has been changed in the database.
Script results by default. You can disable this in the options page.

The debug trace does not collect any messages or the final return value from a function.

To collect and replay a trace

Select the Collect debug trace checkbox in the Debugger Start Parameters window that displays when starting a debug session. See Set Start Parameters for more information.

Note: This checkbox is cleared after every execution.
Select a trace from the Debug Traces window. If needed, you can manually open this window from the Debug menu.
Click to replay a trace.
Use the toolbar to step through the trace.

Tips:

You can generate a coverage report from the trace by clicking .
You can configure debug trace options in Tools | Options | Debugger | General. See General Debugger Options for more information.