FIX: Sproc Created but No Code in Syscomments

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q154001

Bug #: 15417 (SQLBUG_60_RW and SQLBUG_65)

Expand all | Collapse all

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.

Back to the top

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 (http://support.microsoft.com/kb/197177/ ) INF: How to Obtain SQL Server 6.5 Service Pack 5a

For more information, contact your primary support provider.

Back to the top

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

Back to the top

APPLIES TO

Microsoft SQL Server 6.0 Standard Edition
Microsoft SQL Server 6.5 Standard Edition

Back to the top

kbbug kbfix KB154001

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top