Knowledge Base

PRB: A Database User Cannot Debug Stored Procedures That Another User Owns

Article ID: 328173

Article Last Modified on 10/3/2003

APPLIES TO

Microsoft SQL Server 2000 Standard Edition

This article was previously published under Q328173

BUG #: 357336 (SHILOH_BUGS)

SYMPTOMS

When you try to debug a stored procedure that you do not own, you may receive following error message:

Server: Msg 229, Level 14, State 5, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]EXECUTE permission denied on object 'sp_sdidebug', database 'master', owner 'dbo'.

CAUSE

In Transact-SQL Debugging, you cannot debug stored procedures that you do not own after you install SQL Server 2000 Service Pack 3 (SP3).

STATUS

This behavior is by design.

MORE INFORMATION

This behavior is a design change in SQL Server 2000 SP3 to enhance security. This design change includes the following changes:

A database users can only step into stored procedures that they own.
A database owner (DBO) can debug any stored procedure in the database that the DBO owns. (A DBO owns the database and, therefore, all its stored procedures.)
Members of the SysAdmin server role can debug any stored procedure in any database on the server. (A member of the SysAdmin server role owns the server and, therefore, all its databases.)

For more information about Transact-SQL Debugging, see the "Using Transact-SQL Debugger" and "Troubleshooting the Transact-SQL Debugger" topics in SQL Server Books Online.

Keywords: kbprb KB328173

Microsoft KB Archive/328173

Contents