BUG: Stored Proc Script Generation Has "GO" in Middle

Last reviewed: May 1, 1997
Article ID: Q136473

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 11341 (6.00)

SYMPTOMS

When you generate scripts for a stored procedure from SQL Enterprise Manager (SEM) or from another SQLOLE application, the generated script will contain the word "GO" in the middle of the stored procedure code. This can also occur when you select the "Manage, Stored Procedures" option in SEM.

CAUSE

The problem only occurs when multiple stored procedures have been created using the same name with the <name>;<number> option (for example, sp_addrow;1, sp_addrow;2). This option is used to group stored procedures so that they can be dropped with a single DROP PROCEDURE statement.

WORKAROUND

Create the procedures with separate and distinct names rather than using the <name>;<number> option.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: sql6
Keywords : kbbug6.00 kbprg kbtool SSrvDMO SSrvEntMan SSrvProg
Version : 6.0
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: May 1, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.