BUG: Erroneous Message from CREATE TRIGGER Inside EXEC

Last reviewed: April 9, 1997
Article ID: Q153994
The information in this article applies to:
  • Microsoft SQL Server versions 6.0 and 6.5

SYMPTOMS

If, in a single batch, you have an EXEC statement containing a CREATE TRIGGER statement followed by another EXEC statement containing any statement not allowed inside a trigger (for example, CREATE or DROP), the batch aborts with the following message:

   Msg 287, Level 16, State 1
   %s command not allowed within a trigger.

WORKAROUND

Place a command terminator (such as GO) between the two EXEC statements.

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 following script illustrates the problem:

   create table t1 (x int)
   go
   exec("create trigger tr1 on t1 for insert as select @@version")
   exec("create table t2(x int)")
   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.