More on: trigger access control failure on NEW

It turns out that ther only way to successfully define a trigger is to have
the distinguished database-owner userid be the one that executes the
create-trigger statement. Another userid can successfully run a
create-trigger statement, but when the trigger fires it throws an
access-control exception on SYS_INFO.NEW (or .OLD, I'm assuming). There
doesn't seem to be any way to grant the other user access to schema
SYS_INFO, nor is there any way to grant that user access to SYS_INFO.NEW.

 

I'm not sure whether this is a feature or a bug, and depending on my mood I
can argue either way. If this behavior is a feature, I'd suggest also
limiting the CREATE TRIGGER statement to the DBO, so there's no confusion
about who is allowed to create triggers.