BUG: Transact-SQL Debugger Cannot Debug a Stored Procedure that Contains a RAISERROR Statement that Raises any Error with Severity 16 or Higher (280099)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
This article was previously published under Q280099
BUG #: 236327 (Shiloh_bugs)
SYMPTOMS
The debugging options for the Transact-SQL debugger are dimmed (grayed out) when you debug a stored procedure that contains a RAISERROR statement that raises any error with severity 16 or higher.
The Transact-SQL debugger halts execution of any statement after the RAISERROR statement in the stored procedure executes. The Transact-SQL debugger halts execution of any statement when a RAISERROR statement raises any error message with a severity 16 or higher.
If you select the debug option GO (F5) to execute the stored procedure, the stored procedure exits with @RETURN_VALUE = N/A. However, if the RAISERROR statement raises an error with severity 10 or less, the Transact-SQL debugger functions correctly.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 2000.
Modification Type: | Major | Last Reviewed: | 10/3/2003 |
---|
Keywords: | kbbug kbpending KB280099 |
---|
|