Article ID: 328151
Article Last Modified on 10/29/2007
APPLIES TO
- Microsoft SQL Server 2000 Service Pack 3
This article was previously published under Q328151
SUMMARY
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:
MORE INFORMATION
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.
| Debug Client | Default | 'legacy_on' |
|---|---|---|
| Query Analyzer (pre-SP3) | Disabled | Enabled |
| Query Analyzer (SP3) | Enabled | Enabled |
| Visual Studio 5 and 6 | Disabled | Enabled |
| Visual Studio .NET Direct Database Debugging | Enabled | Enabled |
| Visual Studio .NET Application Debugging | Disabled | Enabled |
REFERENCES
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.
Keywords: kbproductlink kbinfo KB328151
