BUG: Erroneous Message from CREATE TRIGGER Inside EXECID: Q153994
|
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.
Place a command terminator (such as GO) between the two EXEC statements.
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.
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
Keywords : kbbug6.50 kbbug6.00
Version : 6.0 6.5
Platform : WINDOWS
Issue type :
Last Reviewed: April 1, 1999