Add "instead of" DDL triggers - by Adam Machanic

Status : 

  Postponed<br /><br />
		Due to current priorities, the product team decided to postpone the resolution of this item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 243986 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 12/7/2006 7:09:43 AM
Access Restriction Public


Currently, DDL triggers are only available as "after" triggers; that is, the code of the trigger runs after the event that caused the trigger to fire has already completed doing everything except committing its transaction -- including all data and log changes.  This eliminates much of the utility of DDL triggers in large or high-concurrency databases, where the triggers might be used to block unauthorized DDL from running.  Unfortunately, since the triggers run "after" the DDL is complete, the user (and, potentially, other users) must wait until the DDL completes, then wait again as it is rolled back, given the current implementation. 
Sign in to post a comment.
Posted by Alvaro R. Dias on 6/30/2012 at 1:11 AM
Any update on this?
Posted by Microsoft on 12/8/2006 at 4:15 PM

Thanks for raising this suggestion. Although this suggestion will not make it for SP2, we will track it for future releases of SQL Server.

Tomer Verona
SQL Server Development