The IDERA SQL Debugger for Microsoft Setup

From DBArtisan
Jump to: navigation, search

Go Up to Setting up the IDERA SQL Debugger

IDERA SQL Debugger for Microsoft requires proper configuration of Server Requirements and Client Requirements.

Important Note about Microsoft SQL Server 2000 Service Pack 4 (SP4)

When running Windows XP SP2, SQL Server 2000 SP4 is required on both the client and the server. To verify this is the case start MS Query Analyzer and press Help > About. The Version SQL should be 8.00.2039.

Important Notes about Microsoft SQL Server 2000 Service Pack 3 (SP3)

By default, after you install Microsoft SQL Server 2000 Service Pack 3 (SP3), you cannot use the T-SQL Debugger.

You may receive the following error message if you try to use the T-SQL Debugger:

“Server: Msg 514, Level 16, State 1, Procedure sp_sdidebug, Line 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to communicate with debugger on [SQL Server Name] (Error = 0x80070005). Debugging disabled for connection 53.”

Microsoft has disabled T-SQL Debugger for Application using earlier T-SQL Debugger clients for security reasons. To enable T-SQL Debugger for these Applications, a member of the sysadmins server role, such as sa must explicitly enable debugging by running the following code:

Exec sp_sdidebug 'legacy_on'
Note: You must repeat this procedure whenever you restart the server.

Server Requirements

IDERA SQL Debugger for Microsoft requires:

  • Windows 2005
  • Windows 2000
  • Microsoft SQL Server version 7.0 or later

Setting Up the Server

There are three parts to setting up the server:

Enabling SQL Debugger for Microsoft on SQL Server SP3

SQL Debugging is disabled by default in SQL Server SP3 and greater. Please refer to Microsoft Support for information regarding enabling the SQL Debugger for Microsoft on SQL Server SP3.

Installing the Microsoft SQL Debugger Interface Subcomponent

The Microsoft server must have the Development Tools, Debugger Interface subcomponent of Microsoft SQL Server. To determine if the Debugger Interface subcomponent is installed, locate the following files in the \Program Files\Common Files\Microsoft Shared\SQL Debugging directory:

  • SQLDBREG.exe
  • SQLDBG.dll

If these files are not in the \Program Files\Common Files\Microsoft Shared\SQL Debugging directory, install them before running the IDERA SQL Debugger for Microsoft.

To install the Debugger Interface subcomponent on the server after the initial installation:

  1. Start Microsoft Visual Studio, Enterprise Edition Setup.
    OR
    Start Microsoft SQL Server Setup.
  2. Select Custom Install.
    Microsoft SQL Server opens the Select Components dialog.
  3. In the Components box, select the Development Tools check box.
  4. In the Sub-components box, select the Debugger Interface check box.
  5. Click Next.
    Microsoft SQL Server proceeds through the Microsoft SQL Server wizard to install the components.

Configuring the Service

To configure the service, see the instructions for your server operating system.

Windows 2000

  1. On the Windows taskbar, click the Start button, click Settings, and then click Control Panel.
  2. Double-click Administrative Tools, and then click Services.
    Windows opens the Services explorer.
  3. In the right pane of the Services explorer, right click MSSQLServer, and then click Properties.
    Windows opens the Net Logon Properties dialog.
  4. Click the Logon tab.
  5. Select the This Account option button.
  6. In the This Account box, type (or browse to locate) the logon user account (including domain name, if necessary) of the person who will be using the IDERA SQL Debugger for Microsoft.
    Note: This person needs admin permissions on the server.
  7. In the Password and Confirm Password boxes, type the password.
  8. Click Apply.
  9. Click the General tab.
  10. Click Start.
    Windows starts the server and applies the changes.

Important Note about Microsoft SQL Server 2000 Service Pack 4 (SP4)

When running Windows XP SP2, SQL Server 2000 SP4 is required on both the client and the server. When running Windows XP SP2, SQL Server 2000 SP4 is required on both the client and the server. To verify this is the case start MS Query Analyzer and press Help > About. The Version SQL should be 8.00.2039.

Important Notes about Microsoft SQL Server 2000 Service Pack 3 (SP3)

By default, after you install Microsoft SQL Server 2000 Service Pack 3 (SP3), you cannot use the T-SQL Debugger.

You may receive the following error message if you try to use the T-SQL Debugger:

“Server: Msg 514, Level 16, State 1, Procedure sp_sdidebug, Line 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to communicate with debugger on [SQL Server Name] (Error = 0x80070005). Debugging disabled for connection 53.”

Microsoft has disabled T-SQL Debugger for Application using earlier T-SQL Debugger clients for security reasons. To enable T-SQL Debugger for these Applications, a member of the sysadmins server role, such as sa must explicitly enable debugging by running the following code:

Exec sp_sdidebug 'legacy_on'
Note: You must repeat this procedure whenever you restart the server.

Configuring DCOM on the Server

To configure DCOM on the server, do the following:

  1. After the server restarts, on the Windows taskbar, click the Start button, and then click Run.
  2. In the Open box, type dcomcnfg.exe.
  3. Click OK.
    Windows opens the Distributed COM Configuration Properties dialog.
  4. Click the Default Security tab.
  5. In the Default Access Permissions box, click Edit Default.
    Windows opens the Registry Value Permissions dialog.
  6. Click Add.
    Windows opens the Add Users and Groups dialog.
  7. In the Names box, select SYSTEM, and then click Add.
  8. Click the Type of Access list, and then click Allow Access.
  9. To let any user use the IDERA SQL Debugger for Microsoft, grant them remote access on the server. To grant remote access, configure their DCOM permissions on the server. In the Names box, click the target users, and then click Add.
    Note: You can add individual users or groups.
  10. Click the Type of Access list, and then click Allow Access.
  11. Click OK.
  12. Restart the server to apply the changes.

Client Requirements

There are three categories of client requirements for the IDERA SQL Debugger for Microsoft:

Operating System

The client must be running one of the following operating systems:

  • Microsoft Windows 95
  • Microsoft Windows 98
  • Microsoft Windows XP

Client Connectivity

When running the Debugger on SQL Server Clients

Before you proceed, verify that the file ssdebugps.dll is registered on the client machine. This file is REQUIRED for debugging and Microsoft only installs it on the server machine and not as a part of a client-only install.

Next you must configure DCOM by following these steps:

  1. At a command prompt, type dcomcnfg, and then press ENTER.
    Component Services opens.
  2. In Component Services, expand Component Services, expand Computers, and then expand My Computer.
  3. On the toolbar, click the Configure My Computer button.
    The My Computer dialog appears.
  4. In the My Computer dialog, click the COM Security tab.
  5. Under Access Permission, click Edit Limits.
    The Access Permission dialog appears.
  6. Under Group or user names, click ANONYMOUS LOGON.
  7. Under Permissions for ANONYMOUS LOGON, select the Remote Access check box, and then click OK.

Finally, you need to go to the Default Properties tab of the MyComputer dialog.

  1. Select None in the Default Authentication Level dropdown menu.
  2. Select Impersonate in the Default Impersonation Level dropdown menu.

For more detailed information, you can refer to Microsoft’s Help: :http://support.microsoft.com/default.aspx?kbid=833977#XSLTH4134121124120121120120

When running Windows XP SP2, SQL Server 2000 SP4 is required on both the client and the server.

For Microsoft SQL the client must have the Client Connectivity component of Microsoft SQL Server.

For Microsoft SQL Server

The client must have the Development Tools, Debugger Interface subcomponent of Microsoft SQL Server. To determine if the Debugger Interface subcomponent is installed, locate the following files in the \Program Files\Common Files\Microsoft Shared\SQL Debugging directory:

  • SQLDBREG.exe
  • SQLDBG.dll

If these files are not in the \Program Files\Common Files\Microsoft Shared\SQL Debugging directory, install them before running the IDERA SQL Debugger for Microsoft.

Installing the Microsoft SQL Debugger Interface on the Client

To install the Debugger Interface subcomponent on the client, do the following:

  1. Start the Microsoft SQL Server Setup program.
  2. Select Custom Install.
    Microsoft SQL Server opens the Select Components dialog.
  3. In the Components box, select the Development Tools check box.
  4. In the Sub-Components box, select the Debugger Interface check box.
  5. Click Next.
    Microsoft SQL Server proceeds through the Microsoft SQL Server Wizard to install the components.