Local and remote debugging

With the debugger's client/server design, you can debug stored procedures that are running remotely on other systems in a network, as well as stored procedures running locally on your workstation.

The debugger server, also known as a debug engine, runs on the same system as the stored procedure you want to debug. This system can be your workstation or a system accessible through a network. If you debug a stored procedure running on your workstation, you are performing local debugging. If you debug a stored procedure running on a system accessible through a network connection, you are performing remote debugging.

With remote debugging, you can run the stored procedure on one system and control it from your workstation. The local system runs the debugger user interface, and the remote system runs both the debug engine and your stored procedure. To be able to debug remotely, you need access to the remote machine where the database and routine you are debugging resides.

When debugging remotely, you might need to configure a rule to turn off your personal firewall. Some corporations have firewalls that might not allow you to connect to an offsite machine. To determine if there are any actions you can take to connect to the remote machine, contact your site administrator

Why Use Remote Debugging?

Remote debugging can prove useful in any number of situations, such as:

Related concepts
Stored procedure debugger
Breakpoints
Related tasks
Using the stored procedure debug launch configuration

Feedback