BUG: T-SQL Debugger Doesn't Allow Stepping Through Stored Procedures with Same Name Owned by Non-DBO Users (296539)


The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)
This article was previously published under Q296539
BUG #: 353351 (SHILOH_BUGS)

SYMPTOMS

If you have two stored procedures with the same name, one owned by the database owner (DBO) and the other owned by a non-DBO user (for example, dbo.test_proc and xyz.test_proc), when trying to debug the xyz.test_proc procedure, neither the DBO nor the xyz user can step through the stored procedure using the T-SQL debugger from SQL Server 2000 Query Analyzer.

The stored procedure is executed immediately under the T-SQL debugger when run from Query Analyzer. Breakpoints can be set after the first execution, but none of the step-through buttons are available. The problem disappears after the DBO-owned stored procedure is dropped, and reappears when it is re-created.

WORKAROUND

Any of the following workarounds can be used:
  • Rename the stored procedure owned by the non-DBO user.
  • Write a wrapper stored procedure to call the stored procedure owned by the non-DBO user, and use the T-SQL debugger to step into the called procedure.
  • Use the debugger from Microsoft Visual Interdev instead of from Query Analyzer.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000.
Modification Type:MajorLast Reviewed:10/3/2003
Keywords:kbbug kbpending KB296539
©2003 Microsoft Corporation. All rights reserved.