FIX: Sproc Created but No Code in Syscomments (154001)

The information in this article applies to:

Microsoft SQL Server 6.0
Microsoft SQL Server 6.5

This article was previously published under Q154001

Bug #: 15417 (SQLBUG_60_RW and SQLBUG_65)

SYMPTOMS

When you create a stored procedure (sproc) or a trigger, view, default, or rule within an EXEC statement, the object is created but no entry for it is recorded in syscomments.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0.

Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base:

197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a

For more information, contact your primary support provider.

MORE INFORMATION

The object can be used as normal, the only problems being that the text is not stored anywhere and that you cannot generate scripts for that object. The following script demonstrates the problem:

   drop proc p1
   go
   exec("create proc p1 as select 1")
   go
   sp_helptext p1
   go
   sp_help p1
   go

Modification Type:	Major	Last Reviewed:	3/14/2006
Keywords:	kbBug kbfix KB154001