Question: > 
> **Possible Duplicate:**  
> 
> [Are database triggers evil?](https://stackoverflow.com/questions/460316/are-database-triggers-evil) 
> 
> 
> 

There is lot of negative information on database triggers, just want to get the community's take on when is it good vs bad.

Answer: 
I think they're OK when they are used to populate a separate, one-off set of tables for things like logging, aggregation etc. for security or creating metadata for example.

When you start altering your "live" data or "looping back" into your biz info tables, that's when they become evil and unwieldy. They are also utterly unnecessary for this. There is nothing that a trigger does that a stored proc cannot do.

I feel like they are SQL's evil equivalent to GOTOs in programming languages. Legal, but to be avoided unless absolutely necessary, and they are NEVER absolutely necessary.
Here are a few articles that should help you figure out by yourself for your needs.

1. [Pros and Cons of Triggers vs. Stored Procedures for Denormalization](https://stackoverflow.com/questions/2088905/pros-and-cons-of-triggers-vs-stored-procedures-for-denormalization) (SO question) ;
2. [Choice Between Stored Procedures, Functions, Views, Triggers, Inline SQL](http://www.paragoncorporation.com/ArticleDetail.aspx?ArticleID=28).

In short, `Triggers` are useful for the processing of massive amount of data, when complex DML has to be conducted. To answer your question, if this is not the case, you got your answer as per when a trigger is bad.