BUG: sproc Created but No Code in syscomments

Last reviewed: April 9, 1997
Article ID: Q154001

The information in this article applies to:

Microsoft SQL Server versions 6.0 and 6.5

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 versions 6.0 and 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

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

Additional query words:
Keywords : kbbug6.00 kbbug6.50
Version : 6.0 6.5
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.