• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 764
  • Last Modified:

trigger on sysobjects

the system allows creation of triggers on sysobjects table. this works fine when one does changes to the sysobjects table after setting 'allow updates' option on. however, the trigger does not fire, when let's say you compile a procedure, which also goes through dropping and recreating a procedure. i am wondering about the difference in two scenarios.
0
sajalk
Asked:
sajalk
1 Solution
 
bretCommented:
The difference, I think, would be that triggers are designed to fire on certain commands:  insert, update, and delete.  Drop procedures and create procedure are not one of those commands,
so the trigger doesn't fire.

Actually, I'm a bit surprised that they fire at all for system tables, as in the 4.2 version triggers could be created on system tables but would never fire (and this was documented).
But it sounds like Microsoft has enhanced them somewhat.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now