BUG: Erroneous Message from CREATE TRIGGER Inside EXEC (153994)

The information in this article applies to:

Microsoft SQL Server 6.0
Microsoft SQL Server 6.5

This article was previously published under Q153994

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.

RESOLUTION

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

Modification Type:	Minor	Last Reviewed:	3/14/2005
Keywords:	kbBug KB153994