This article was previously published under Q310650
This article has been archived. It is offered "as is" and will no longer be updated.
Since the release of SQL Server 2000, Microsoft has identified a number of issues between SQL Server 2000 and the Visual Basic 6.0 T-SQL Stored Procedure Debugger add-in, which originally released in 1998. This article lists the most significant issues.
For additional information about any of the issues that are listed, please consult the referenced Microsoft Knowledge Base articles:
In Visual Basic Service 6.0 Pack 4 (SP4) and earlier, the debugger does not correctly parse the SQL Server 2000 @RETURN_VALUE parameter, which has been renamed from RETURN_VALUE. As a result, stored procedure parameters are listed incorrectly in the debugger window, and the procedure will not execute correctly. Visual Basic 6.0 SP5 resolves this issue.
272074 FIX: T-SQL Debugger Parses SQL Server 2000 Return Value Incorrectly
The debugger does not work with a named instance of SQL Server 2000.
310647 BUG: Visual Basic 6.0 T-SQL Debugger Fails Against SQL Server 2000 Named Instance
The debugger does not work with SQL Server 2000 Service Pack 1. This problem has been fixed in SQL Server 2000 Service Pack 2.
The SQDBG_SS folder on CD 2 of Microsoft Visual Studio or Visual Basic Enterprise Edition contains a setup program for the automated installation of the debugging components that are required on the SQL Server. However, this setup program fails on SQL Server 2000, and you must install the components manually.
For additional information about the T-SQL Debugger add-in and other known issues, click the article numbers below to view the articles in the Microsoft Knowledge Base:
166280 DOC: T-SQL Debugger Server Setup Provides Incorrect Location
170496 INF: Tips for Debugging Stored Procedures from Visual Basic
172099 PRB: T-SQL - Running Remote and Local SQL Debugging
175868 BUG: T-SQL Debugger Does Not Run on NT with User Account
179023 FIX: T-SQL Debugger Hangs When User Has No Execute Permission
190211 PRB: Problems When Visual Basic 5.0 and 6.0 Are Installed on the Same System
190212 BUG: Add-Ins Only Visible to the User Who Installs VB
190451 BUG: Exiting VB While T-SQL Debugger Is Running Causes Hang
191513 BUG: T-SQL Debugger Is Not Invoked Calling Second Stored Procedure
200888 PRB: Cannot Invoke T-SQL Debugger to Automatically Appear Using ADO
223060 FIX: T-SQL Shows Incorrect Parameters in Local Variables Window
254464 PRB: Can't Add the T-SQL Debugger to the Visual Basic Add-in Manager
281297 FIX: Visual Studio 6.0 T-SQL Debugger Buffer Overflow