Article ID: 280101 - View products that this article applies to.
This article was previously published under Q280101
This article describes the limitations of Transact-SQL Debugger in SQL Server 2000. This article also provides guidelines and directions to troubleshoot basic problems related to Transact-SQL Debugger. However, this is not an exhaustive list, and some problems may be specific to your environment.
Limitations with Transact-SQL Debugger
Troubleshooting the Transact-SQL Debugger
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/272074/EN-US/ )FIX: T-SQL Debugger Parses SQL Server 2000 Return Value Wrong
(http://support.microsoft.com/kb/281535/EN-US/ )PRB: Error Debugging Procedure with sql_variant Input Parameter
(http://support.microsoft.com/kb/270061/EN-US/ )BUG: Access Violation Occurs When You Debug Stored Procedure
(http://support.microsoft.com/kb/175868/EN-US/ )BUG: T-SQL Debugger Does Not Run on NT with User Account
(http://support.microsoft.com/kb/328173/EN-US/ )PRB: A Database User Cannot Debug Stored Procedures That Another User Owns
(http://support.microsoft.com/kb/317241/EN-US/ )PRB: Renaming a Host Computer for SQL Server Causes Stored Procedure Debug to Fail
(http://support.microsoft.com/kb/296539/EN-US/ )BUG: T-SQL Debugger Doesn't Allow Stepping Through Stored Procedures with Same Name Owned by Non-DBO Users
(http://support.microsoft.com/kb/328151/EN-US/ )INF: T-SQL Debugger Is Turned Off By Default for Earlier Clients After You Install SQL Server 2000 Service Pack 3