More on Instead of Triggers

Did you know that you can create an instead of trigger on a view as well as a table? In this video we'll show an example of the syntax and then show how instead of triggers can be used to 'throw away' data that doesn't fit our scenario without raising an error.

Andy Warren is a software trainer focusing on SQL Server, a member of the PASS Board of Directors, and a principal in this site - SQLShare.com.

Dan on 10/19/2009

Interesting!

Tonci on 10/19/2009

Simple and to the point!

Thad Moorer on 10/20/2009

Very useful and practical concept.

bhaskar on 10/20/2009

Good one

Harvey Schwartz on 10/20/2009

This was very useful as I need to soon create my first Intead of triggers. Is it possible to get a copy of the SQL used to define the trigger in this example?

Julie Breutzmann on 10/20/2009

Can you provide an example of when one might use this? I would think that most times one would WANT to know if an insert was NOT occurring.

geungerjr on 10/20/2009

Where is this useful?

David on 10/23/2009

very illustrative! thanks!

Prasanna Prabhu on 10/24/2009

Great Video

Sandip on 12/21/2009

great.

A Alagu Ganesh on 1/20/2010

Good

Monty on 3/4/2010

The video does a good job of presenting the how-to but the example does not use a good case scenario. If you are not going to allow the insert then what do you return to the user?

desmond on 7/7/2010

I wasnt sure initialy why you'd want to put the trigger on a view instead of directly onto the table. It also raised the question, can you do *after* triggers on a view. But overall it was a superb and thought provoking coverage. Thanks again.

A Alagu Ganesh on 10/14/2010

Good

37F4DA828D on 1/21/2011

love it - have never done a trigger based on a view - must rememer this one

Satyabodhi Densmore on 1/28/2011

Should show insert, update, and delete over a view over a join.