This article was previously published under Q328151
This article has been archived. It is offered "as is" and will no longer be updated.
By default, after you install Microsoft SQL Server 2000 Service Pack 3 (SP3), you cannot use the T-SQL Debugger if you are using a version of Query Analyzer that is earlier than Microsoft SQL Server 2000 SP3 or a version of Microsoft Visual Studio earlier than Microsoft Visual Studio .NET.
You may receive the following error message if you try to use the T-SQL Debugger from an earlier client:
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.
Note Versions of Query Analyzer that are earlier than SQL Server 2000 SP3 and versions of Visual Studio that are earlier than Visual Studio .NET are referred to as "earlier clients" in this article.
Microsoft has disabled T-SQL Debugger for earlier clients for security reasons. To enable T-SQL Debugger for earlier clients, a member of the sysadmins server role, such as sa must explicitly enable debugging by running the following code:
Exec sp_sdidebug 'legacy_on'
You must repeat this procedure whenever you restart the server. Microsoft does not recommend that you use T-SQL Debugger on a production server.
To disable T-SQL Debugger for earlier clients, a member of the sysadmins server role can run the following code:
Exec sp_sdidebug 'legacy_off'
The following table describes the default behavior of Transact-SQL Debugger with SQL Server SP3.
Query Analyzer (pre-SP3)
Query Analyzer (SP3)
Visual Studio 5 and 6
Visual Studio .NET Direct Database Debugging
Visual Studio .NET Application Debugging
For more information about T-SQL Debugger, see the "Using Transact-SQL Debugger" and "Troubleshooting the Transact-SQL Debugger" topics in SQL Server Books Online.