Open topic with navigation

Learn more about Toad for SQL Server at Quest.com Find solutions and downloads at the Toad for SQL Server Support Portal

Configure SQL Server Debugging

Debugging Prerequisites

Before configuring the Debugger, verify that the following prerequisites have been met:

• Disable all firewalls or open corresponding ports. Windows XP Service Pack 2 includes an embedded Windows firewall that should be disabled or ports opened as well. Specifically, the TCP 135 port must be opened and the Toad.exe must be added to the Exceptions list. The same is true for the remote (SQL Server) machine - TCP 135 port must be opened and sqlservr.exe must be added to the Exceptions list.
• Stop any antivirus software that can lock the corresponding components, settings, etc.

• Check your security policy because it may include an access lock to the remote server.

  Notes:

  • The security policy can be applied to the domain or local computer.
  • Currently, you cannot debug CLR stored procedures.

Platforms Tested for Debugging Support

The following platforms have been tested for debugging support.

Note: The Service Pack on the client must match the Service Pack on the server unless specified otherwise.

SQL Server 2012 Platforms Tested for Debugging
Client	Server
	2003 EE (SP2)	2000 (SP4)	2000 Pro (SP4)	XP Pro (SP3)	Vista	Server 2008	7
2003 EE (SP1)
XP Pro (SP3)
Vista
Server 2008
7

 

SQL Server 2008 Platforms Tested for Debugging
Client	Server
	2003 EE (SP2)	2000 (SP4)	2000 Pro (SP4)	XP Pro (SP3)	Vista	Server 2008	7
2003 EE (SP1)
XP Pro (SP3)
Vista
Server 2008
7

 

SQL Server 2005 Platforms Tested for Debugging
Client	Server
	2003 EE (SP1)	2000 (SP4)	2000 Pro (SP4)	XP Pro (SP3)	Vista	Server 2008	7
2003 EE (SP1)
XP Pro (SP3)
Vista
Server 2008
7

 

SQL Server 2000 (SP4) Platforms Tested for Debugging
Client	Server
	2003 EE (SP1)	2000 (SP4)	2000 Pro (SP4)	XP Pro (SP2)	Vista	Server 2008	7
2003 EE (SP1)
XP Pro (SP2)				(Local server)
Vista
Server 2008
7

Configure Debugging for SQL Server 2012

To debug locally, perform the following on the Toad client

1. Install the SQL Server 2012 Client Tools on the Toad client.

2. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

To debug remotely, perform the following

1. Install the SQL Server 2012 Client Tools on the Toad client.

2. Set the following permission. Your server login must also be a member of the sysadmin role. This login can be your Windows user account (Windows authentication), or a SQL Server login (SQL Server authentication).

   To create a server login from your Windows account and add it to the sysadmin role, a user who already has sysadmin privileges must execute the following:

   sp_addsrvrolemember 'Domain\Name', 'sysadmin'

   where Domain\Name is your Windows login.

3. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

Configure Debugging for SQL Server 2008

To debug locally, perform the following on the Toad client

1. Install the SQL Server 2008 Client Tools on the Toad client.

2. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

To debug remotely, perform the following

1. Install the SQL Server 2008 Client Tools on the Toad client.
2. Make sure the following permissions are set:
   • Your Windows account that Toad is running under must be a member of sysadmin server role in the SQL Server being debugged.

   • Your server login must also be a member of the sysadmin role. This login can be your Windows user account (Windows authentication), or a SQL Server login (SQL Server authentication).

     To create a server login from your Windows account and add it to the sysadmin role, a user who already has sysadmin privileges must execute the following:

     sp_addsrvrolemember 'Domain\Name', 'sysadmin'

     where Domain\Name is your Windows login.

3. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

Configure Debugging for SQL Server 2005

To debug locally, perform the following on the Toad client

1. Install the SQL Server 2005 Workstation Component option of the SQL Server 2005 installation.

2. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

To debug remotely, perform the following

1. Complete the following:
   1. Install the SQL Server 2005 Workstation Components option of the SQL Server 2005 installation on the Toad client.

   2. Copy and register the ssdebugps.dll (debugging host component) on both the client and server. This file is located by default in the following directory on the server where SQL Server 2005 is installed:

      C:\Program Files\ Common Files\Microsoft Shared\SQL Debugging

      To register this file, open a command prompt and enter the following command:

      regsvr32 ssdebugps.dll

      Note: If you are unable to locate this file, you can run the remote debugging setup component (rdbgsetup.exe). This file is located by default in the following directory on the server where SQL Server 2005 is installed:

      C:\Program Files\Microsoft SQL Server\90\Shared\1033

2. Make sure the following permissions are set:
   • Your Windows account that Toad is running under must be a member of sysadmin server role in the SQL Server being debugged.

   • Your server login must also be a member of the sysadmin role. This login can be your Windows user account (Windows authentication), or a SQL Server login (SQL Server authentication).

     To create a server login from your Windows account and add it to the sysadmin role, a user who already has sysadmin privileges must execute the following:

     sp_addsrvrolemember 'Domain\Name', 'sysadmin'

     where Domain\Name is your Windows login.

3. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

Configure Debugging for SQL Server 2000

To debug locally, perform the following on the Toad client

1. Make sure that SQL Server 2000 with Service Pack 3 or Service Pack 4 is installed on the server.
2. Install the SQL Server Client Tools on the Toad client.

3. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

To debug remotely, perform the following

1. Complete the following:
   1. Make sure that SQL Server 2000 with Service Pack 3 or Service Pack 4 is installed on the server.
   2. Install the SQL Server Client Tools on the Toad client.

   3. Copy and register the sqldbg.dll and sqldbreg2.exe (debugging host components) on both the Toad client and server. These files are located by default in the following directory on the server where SQL Server 2000 is installed:

      C:\Program Files\Common Files\Microsoft Shared\SQL Debugging

      To register these files, open a command prompt and enter the following commands:

      regsvr32 sqldbg.dlls

      qldbreg2.exe /RegServer

      Note: The Remote Procedure Call (RPC) service should be started on both the Toad client and server.

2. Make sure the following permissions are set:
   • Your Windows account that Toad is running under must be a member of the sysadmin server role for the instance you are debugging.

   • Your server login must also be a member of the sysadmin role. This login can be your Windows user account (Windows authentication), or a SQL Server login (SQL Server authentication).

     To create a server login from your Windows account and add it to the sysadmin role, a user who already has sysadmin privileges must execute the following:

     sp_addsrvrolemember 'Domain\Name', 'sysadmin'

     where Domain\Name is your Windows login.

   • DCOM Access permissions must be granted for the system account and the group or user who needs access.To verify permissions:
     1. Open a command prompt and run dcomcnfg.exe. 
     2. Expand Component Services, Computers.
     3. Right-click My Computer and select Properties.
     4. Select the COM Security tab.

     5. Under Access Permissions, click Edit Default, and verify permissions.

        Note: By default, Windows administrators on a computer running SQL Server are SQL Server sysadmins on that computer.

3. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

Related Topics

Set Up Debugging

About Debugging SQL