Article ID: 310650 - Last Review: September 29, 2006 - Revision: 4.2

INFO: Known Issues with the Visual Basic T-SQL Debugger and SQL Server 2000

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
This article was previously published under Q310650
Expand all | Collapse all

SUMMARY

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.
Back to the top

MORE INFORMATION

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  (http://support.microsoft.com/kb/272074/EN-US/ ) 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  (http://support.microsoft.com/kb/310647/EN-US/ ) 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.
Back to the top

REFERENCES

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  (http://support.microsoft.com/kb/166280/EN-US/ ) DOC: T-SQL Debugger Server Setup Provides Incorrect Location
170496  (http://support.microsoft.com/kb/170496/EN-US/ ) INF: Tips for Debugging Stored Procedures from Visual Basic
172099  (http://support.microsoft.com/kb/172099/EN-US/ ) PRB: T-SQL - Running Remote and Local SQL Debugging
175868  (http://support.microsoft.com/kb/175868/EN-US/ ) BUG: T-SQL Debugger Does Not Run on NT with User Account
179023  (http://support.microsoft.com/kb/179023/EN-US/ ) FIX: T-SQL Debugger Hangs When User Has No Execute Permission
190211  (http://support.microsoft.com/kb/190211/EN-US/ ) PRB: Problems When Visual Basic 5.0 and 6.0 Are Installed on the Same System
190212  (http://support.microsoft.com/kb/190212/EN-US/ ) BUG: Add-Ins Only Visible to the User Who Installs VB
190451  (http://support.microsoft.com/kb/190451/EN-US/ ) BUG: Exiting VB While T-SQL Debugger Is Running Causes Hang
191513  (http://support.microsoft.com/kb/191513/EN-US/ ) BUG: T-SQL Debugger Is Not Invoked Calling Second Stored Procedure
200888  (http://support.microsoft.com/kb/200888/EN-US/ ) PRB: Cannot Invoke T-SQL Debugger to Automatically Appear Using ADO
223060  (http://support.microsoft.com/kb/223060/EN-US/ ) FIX: T-SQL Shows Incorrect Parameters in Local Variables Window
254464  (http://support.microsoft.com/kb/254464/EN-US/ ) PRB: Can't Add the T-SQL Debugger to the Visual Basic Add-in Manager
281297  (http://support.microsoft.com/kb/281297/EN-US/ ) FIX: Visual Studio 6.0 T-SQL Debugger Buffer Overflow
Back to the top
APPLIES TO
  • Microsoft Visual Basic Enterprise Edition for Windows 6.0
  • Microsoft SQL Server 2000 Standard Edition
Back to the top
Keywords: 
kbdatabase kbinfo kbtsql KB310650
Back to the top